{"id":1099,"date":"2026-02-25T10:35:54","date_gmt":"2026-02-25T10:35:54","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/acceptance-criteria-user-stories\/"},"modified":"2026-02-25T10:35:54","modified_gmt":"2026-02-25T10:35:54","slug":"acceptance-criteria-user-stories","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/acceptance-criteria-user-stories\/","title":{"rendered":"Acceptance Criteria That Clarify Definition of Done"},"content":{"rendered":"<p>About 6 out of 10 teams I\u2019ve worked with define \u201cdone\u201d only in vague terms like \u201call tasks complete\u201d or \u201ccode reviewed.\u201d That\u2019s not enough. Without clear acceptance criteria, stories become ambiguous, testing becomes inconsistent, and the Definition of Done collapses into a checklist of assumptions.<\/p>\n<p>Acceptance criteria are the bridge between what the user wants and what the team commits to delivering. They\u2019re not just a list of tests\u2014they\u2019re a shared understanding. When written well, they make the Definition of Done concrete, verifiable, and aligned with business value.<\/p>\n<p>What you\u2019ll gain here is a practical guide to crafting acceptance criteria that stop ambiguity, reduce rework, and turn conversations into actionable outcomes. I\u2019ll show you real formats, trade-offs, and how to avoid the common trap of writing criteria that pass but miss the point.<\/p>\n<h2>Why Acceptance Criteria Matter in Agile User Stories<\/h2>\n<p>Acceptance criteria aren\u2019t optional documentation\u2014they\u2019re part of the story\u2019s DNA. They define what success looks like from the user\u2019s perspective.<\/p>\n<p>When teams skip or rush acceptance criteria, two things happen: misunderstandings grow, and the Definition of Done becomes arbitrary. A story marked \u201cdone\u201d may lack critical checks, fail in production, or miss key user scenarios.<\/p>\n<p>As a mentor, I\u2019ve seen teams spend hours debugging issues because they assumed the user \u201cwouldn\u2019t need\u201d a certain feature. That\u2019s not a bug\u2014it\u2019s a missing acceptance criterion.<\/p>\n<h3>What Acceptance Criteria Are (and Aren\u2019t)<\/h3>\n<p>Acceptance criteria are <strong>verifiable conditions<\/strong> that a story must meet. They\u2019re not technical specs. They\u2019re not test scripts. They\u2019re not implementation details.<\/p>\n<p>They answer: <em>When can we say the user\u2019s goal is actually fulfilled?<\/em><\/p>\n<p>Common mistakes:<\/p>\n<ul>\n<li>Writing criteria in developer jargon like \u201cbackend API returns 200.\u201d<\/li>\n<li>Using vague terms like \u201cworks correctly\u201d or \u201cdata shows up.\u201d<\/li>\n<li>Creating so many criteria that the story becomes unwieldy.<\/li>\n<\/ul>\n<h2>Proven Formats for Effective Acceptance Criteria<\/h2>\n<p>There\u2019s no single correct format, but certain patterns work consistently across teams. Choose one that fits your context and stick with it.<\/p>\n<h3>Given-When-Then (GWT) Format<\/h3>\n<p>This format is excellent for behavior-driven development (BDD) and real-world scenarios.<\/p>\n<pre><code>Given the user is on the login page\nWhen they enter valid credentials\nThen they should be redirected to the dashboard<\/code><\/pre>\n<p>Use this when the story involves a sequence of actions and expected results. It forces clarity about state, action, and outcome.<\/p>\n<h3>Scenario: One Example, One Outcome<\/h3>\n<p>Structure each criterion as a standalone scenario. This avoids confusion and keeps the focus on one behavior at a time.<\/p>\n<ul>\n<li><strong>Scenario 1:<\/strong> User logs in with correct credentials \u2192 redirected to dashboard<\/li>\n<li><strong>Scenario 2:<\/strong> User logs in with incorrect email \u2192 error message shown<\/li>\n<li><strong>Scenario 3:<\/strong> User logs in with blank password \u2192 validation error appears<\/li>\n<\/ul>\n<p>Each scenario should be testable and independent. Don\u2019t combine multiple behaviors in one criterion.<\/p>\n<h3>Business Language + Acceptance Criteria<\/h3>\n<p>For non-technical stakeholders, keep language simple and goal-focused.<\/p>\n<p>Story: <em>As a customer, I want to reset my password so I can regain access to my account.<\/em><\/p>\n<p>Acceptance Criteria:<\/p>\n<ul>\n<li>Given I\u2019m on the password reset page, when I enter my email, then I should receive a confirmation message.<\/li>\n<li>Given I\u2019ve received the reset email, when I click the link, then I should be taken to a page to enter a new password.<\/li>\n<li>Given I\u2019ve entered a new password, when I submit it, then my password should be updated and I should be redirected to the login page.<\/li>\n<\/ul>\n<p>These are clear, specific, and grounded in user behavior\u2014not implementation.<\/p>\n<h2>How to Write Acceptance Criteria That Work<\/h2>\n<p>Here\u2019s a step-by-step approach I\u2019ve used with teams across fintech, healthcare, and SaaS:<\/p>\n<ol>\n<li><strong>Start with the story goal.<\/strong> Ask: \u201cWhat does the user truly need?\u201d Avoid jumping to \u201chow.\u201d<\/li>\n<li><strong>Break it into behaviors.<\/strong> Think: \u201cWhat are the key interactions the user will have?\u201d<\/li>\n<li><strong>Write each behavior as a scenario.<\/strong> Use <em>Given-When-Then<\/em> or plain English.<\/li>\n<li><strong>Add edge cases.<\/strong> What if the data is missing? What if the user is offline?<\/li>\n<li><strong>Review with the team.<\/strong> Does QA know how to test it? Does the developer understand the intent?<\/li>\n<\/ol>\n<p>Don\u2019t write criteria in isolation. They\u2019re a conversation starter, not a document.<\/p>\n<h3>Common Pitfalls and How to Avoid Them<\/h3>\n<p>Even with good intentions, teams often fall into traps:<\/p>\n<ul>\n<li><strong>Too vague:<\/strong> \u201cUser receives confirmation.\u201d \u2192 <em>What confirmation? When? To whom?<\/em><\/li>\n<li><strong>Too technical:<\/strong> \u201cAPI returns status 200.\u201d \u2192 <em>What does that mean for the user?<\/em><\/li>\n<li><strong>Too many criteria:<\/strong> Overloading a story with 10+ acceptance criteria hides the core value.<\/li>\n<\/ul>\n<p>Ask: <em>Can a tester write a test from this? Can a new team member understand it without context?<\/em><\/p>\n<h2>Acceptance Criteria and the Definition of Done<\/h2>\n<p>Acceptance criteria are the foundation of the <strong>Definition of Done (DoD)<\/strong>. But only if they\u2019re clear and measurable.<\/p>\n<p>When teams say \u201cthe story is done,\u201d they mean: <em>all acceptance criteria have passed.<\/em><\/p>\n<p>This is where many fail. Let\u2019s look at a real example:<\/p>\n<table>\n<tbody>\n<tr>\n<th>DoD Checklist<\/th>\n<th>Example: User Login Story<\/th>\n<\/tr>\n<tr>\n<td>Acceptance criteria defined<\/td>\n<td>\u2713<\/td>\n<\/tr>\n<tr>\n<td>Code reviewed<\/td>\n<td>\u2713<\/td>\n<\/tr>\n<tr>\n<td>Unit tests pass<\/td>\n<td>\u2713<\/td>\n<\/tr>\n<tr>\n<td>Integration tests pass<\/td>\n<td>\u2713<\/td>\n<\/tr>\n<tr>\n<td>Acceptance tests passed<\/td>\n<td>\u2717 (No acceptance criteria defined)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>If acceptance criteria are missing or vague, the DoD is incomplete. That story is not truly \u201cdone\u201d \u2014 it\u2019s just \u201cwritten.\u201d<\/p>\n<h3>Definition of Done Examples<\/h3>\n<p>Here are two clear examples from real teams:<\/p>\n<p><strong>Example 1: E-commerce Checkout<\/strong><\/p>\n<ul>\n<li>When the user clicks \u201cComplete Order,\u201d a confirmation page shows the order summary and number.<\/li>\n<li>When the order is placed, an email is sent to the user with order details within 30 seconds.<\/li>\n<li>When the user is logged in, the order appears in their \u201cMy Orders\u201d history.<\/li>\n<\/ul>\n<p><strong>Example 2: User Profile Update<\/strong><\/p>\n<ul>\n<li>When the user updates their email, a confirmation message appears.<\/li>\n<li>When the email is changed, the user must verify it via a link sent to the old and new email.<\/li>\n<li>When the user tries to log in with the old email, they are prompted to verify the new one.<\/li>\n<\/ul>\n<p>Each of these is testable, user-focused, and directly tied to business value. That\u2019s how you build a trustworthy Definition of Done.<\/p>\n<h2>When to Avoid Acceptance Criteria (and What to Do Instead)<\/h2>\n<p>Not every story needs formal acceptance criteria. Some are too simple or already covered by other rules.<\/p>\n<p>For example:<\/p>\n<ul>\n<li>A button label change: \u201cUpdate Profile\u201d \u2192 \u201cSave Changes\u201d<\/li>\n<li>Minor UI layout fix: \u201cAlign form fields to center\u201d<\/li>\n<\/ul>\n<p>But even here, ask: <em>Does this change affect user experience? Could someone misunderstand it?<\/em> If yes, add a simple acceptance criterion.<\/p>\n<p>For these light stories, use a <em>one-liner criterion<\/em> or link to a design specification.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How many acceptance criteria should a user story have?<\/h3>\n<p>Between 3 and 5 is ideal. More than that, and the story becomes hard to test and maintain. Focus on the most critical behaviors that deliver value.<\/p>\n<h3>Can acceptance criteria be written in plain English?<\/h3>\n<p>Absolutely. In fact, they should be. The goal is clarity across roles\u2014product owner, developer, QA, UX. Use natural language, not technical syntax.<\/p>\n<h3>Are acceptance criteria the same as test cases?<\/h3>\n<p>No. Acceptance criteria define <em>what<\/em> to test. Test cases define <em>how<\/em> to test it. But every acceptance criterion should map to at least one test case.<\/p>\n<h3>What if acceptance criteria change during development?<\/h3>\n<p>That\u2019s normal. The story is a conversation, not a contract. If new insight emerges, discuss it with the team and update the criteria. But never ignore a change in user need.<\/p>\n<h3>Do acceptance criteria apply to non-interactive features like reporting?<\/h3>\n<p>Yes. For example: \u201cAs a manager, I want a weekly sales report so I can track performance.\u201d Acceptance criteria: \u201cThe report includes total sales, top 5 products, and comparison to last week.\u201d<\/p>\n<h3>How do I ensure acceptance criteria are verifiable?<\/h3>\n<p>Ask: \u201cCan we prove this is true?\u201d If yes, it\u2019s verifiable. If it depends on \u201cthe user will like it,\u201d it\u2019s not. Replace subjective language with measurable outcomes.<\/p>\n<p>Acceptance criteria user stories aren\u2019t just about writing\u2014it\u2019s about building trust. When criteria are clear, teams deliver with confidence. When they\u2019re vague, rework, frustration, and scope creep follow.<\/p>\n<p>Use the formats here. Apply them consistently. Review them in refinement. Make them a shared commitment.<\/p>\n<p>Because a user story is only as strong as its acceptance criteria.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>About 6 out of 10 teams I\u2019ve worked with define \u201cdone\u201d only in vague terms like \u201call tasks complete\u201d or \u201ccode  [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1095,"menu_order":3,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-1099","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Acceptance Criteria for Agile User Stories<\/title>\n<meta name=\"description\" content=\"Learn how to write effective acceptance criteria for user stories that clarify the Definition of Done. Practical examples, formats, and agile acceptance criteria guidelines for teams.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/acceptance-criteria-user-stories\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Acceptance Criteria for Agile User Stories\" \/>\n<meta property=\"og:description\" content=\"Learn how to write effective acceptance criteria for user stories that clarify the Definition of Done. Practical examples, formats, and agile acceptance criteria guidelines for teams.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/acceptance-criteria-user-stories\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills\u65e5\u672c\u8a9e\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"7\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/acceptance-criteria-user-stories\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/acceptance-criteria-user-stories\/\",\"name\":\"Acceptance Criteria for Agile User Stories\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-02-25T10:35:54+00:00\",\"description\":\"Learn how to write effective acceptance criteria for user stories that clarify the Definition of Done. Practical examples, formats, and agile acceptance criteria guidelines for teams.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/acceptance-criteria-user-stories\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/acceptance-criteria-user-stories\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/acceptance-criteria-user-stories\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Write Effective User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Building Strong Stories Step by Step\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Acceptance Criteria That Clarify Definition of Done\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Acceptance Criteria for Agile User Stories","description":"Learn how to write effective acceptance criteria for user stories that clarify the Definition of Done. Practical examples, formats, and agile acceptance criteria guidelines for teams.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/acceptance-criteria-user-stories\/","og_locale":"ja_JP","og_type":"article","og_title":"Acceptance Criteria for Agile User Stories","og_description":"Learn how to write effective acceptance criteria for user stories that clarify the Definition of Done. Practical examples, formats, and agile acceptance criteria guidelines for teams.","og_url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/acceptance-criteria-user-stories\/","og_site_name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","twitter_card":"summary_large_image","twitter_misc":{"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"7\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/acceptance-criteria-user-stories\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/acceptance-criteria-user-stories\/","name":"Acceptance Criteria for Agile User Stories","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-02-25T10:35:54+00:00","description":"Learn how to write effective acceptance criteria for user stories that clarify the Definition of Done. Practical examples, formats, and agile acceptance criteria guidelines for teams.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/acceptance-criteria-user-stories\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/acceptance-criteria-user-stories\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/acceptance-criteria-user-stories\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ja\/"},{"@type":"ListItem","position":2,"name":"How to Write Effective User Stories","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/"},{"@type":"ListItem","position":3,"name":"Building Strong Stories Step by Step","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/"},{"@type":"ListItem","position":4,"name":"Acceptance Criteria That Clarify Definition of Done"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website","url":"https:\/\/skills.visual-paradigm.com\/ja\/","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","url":"https:\/\/skills.visual-paradigm.com\/ja\/","logo":{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills\u65e5\u672c\u8a9e"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/1099","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/1099\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/1095"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=1099"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=1099"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}