{"id":680,"date":"2026-02-25T10:22:45","date_gmt":"2026-02-25T10:22:45","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/missing-acceptance-criteria-agile\/"},"modified":"2026-03-02T09:13:52","modified_gmt":"2026-03-02T09:13:52","slug":"missing-acceptance-criteria-agile","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/missing-acceptance-criteria-agile\/","title":{"rendered":"Ignoring Acceptance Criteria and Definition of Done"},"content":{"rendered":"<p>Stories are meant to be conversation starters \u2014 not final contracts. But too many teams treat them as if they were. I\u2019ve seen sprint after sprint end with stories marked \u201cdone,\u201d only to fail in QA because the acceptance conditions were never defined. That\u2019s not a bug. It\u2019s a systemic flaw.<\/p>\n<p>When acceptance criteria go missing, you\u2019re not just delaying delivery \u2014 you\u2019re building on sand. The team guesses what \u201cdone\u201d means. The PO assumes the feature works. QA tests what they think is correct. The result? Re-work, scope creep, and a backlog that accumulates invisible debt.<\/p>\n<p>This chapter cuts through the noise. You\u2019ll learn how to define actionable, testable criteria that prevent misunderstandings. I\u2019ll share real examples from my years working with teams across fintech, healthcare, and SaaS \u2014 from startups to enterprise. The goal isn\u2019t perfection. It\u2019s clarity.<\/p>\n<h2>Why Missing Acceptance Criteria Breaks Agile Delivery<\/h2>\n<p>Acceptance criteria are not optional extras. They are the bridge between intent and implementation. Without them, a story becomes a black box.<\/p>\n<p>Imagine a story: \u201cAs a user, I want to reset my password so I can regain access.\u201d Without criteria, no one knows what \u201creset\u201d means. Does it mean:<\/p>\n<ul>\n<li>Send an email with a link?<\/li>\n<li>Allow temporary access via security code?<\/li>\n<li>Require multi-factor authentication?<\/li>\n<\/ul>\n<p>That ambiguity leads to assumptions. And assumptions drive rework. I\u2019ve seen teams spend days building a feature that didn\u2019t even align with the user\u2019s actual need \u2014 all because the acceptance rules were never defined.<\/p>\n<p>Definition of done issues arise when the team\u2019s \u201cdone\u201d means something different than the PO\u2019s. One team marked stories \u201cdone\u201d after code review, only to discover the UI wasn\u2019t tested. Another assumed \u201cdone\u201d meant \u201cdeployed\u201d \u2014 even though no regression tests passed.<\/p>\n<h3>The Hidden Cost of Unwritten Rules<\/h3>\n<p>Here\u2019s what happens when you skip acceptance criteria:<\/p>\n<ul>\n<li><strong>Re-work at scale:<\/strong> Features built without testable conditions often fail in staging or production.<\/li>\n<li><strong>Scope creep:<\/strong> The PO keeps adding \u201cminor changes\u201d because the original story wasn\u2019t clear.<\/li>\n<li><strong>Team frustration:<\/strong> Developers feel stuck, not because they can\u2019t code, but because they can\u2019t tell when they\u2019re done.<\/li>\n<li><strong>PO distrust:<\/strong> If delivery is inconsistent, the PO loses confidence in the team\u2019s ability to deliver value.<\/li>\n<\/ul>\n<p>It\u2019s not just about testing. It\u2019s about shared understanding.<\/p>\n<h2>How to Build Testable Story Definitions<\/h2>\n<p>Testable story definition isn\u2019t about writing more. It\u2019s about writing better.<\/p>\n<p>Start with a simple rule: every story must have acceptance criteria that answer three questions:<\/p>\n<ol>\n<li>What does success look like?<\/li>\n<li>What are the edge cases?<\/li>\n<li>How will we verify it?<\/li>\n<\/ol>\n<p>Let\u2019s walk through a real example.<\/p>\n<h3>Before: A Vague Story<\/h3>\n<p><em>As a customer, I want to see my order history so I can track past purchases.<\/em><\/p>\n<p>Too broad. No clear success conditions. No boundaries.<\/p>\n<h3>After: A Testable Story<\/h3>\n<p><em>As a customer, I want to see my order history so I can track past purchases.<\/em><\/p>\n<p><strong>Acceptance Criteria:<\/strong><\/p>\n<ul>\n<li>When I visit the order history page, I see at least 10 most recent orders.<\/li>\n<li>Each order shows the date, total amount, and status (e.g., Delivered, Processing).<\/li>\n<li>If I have no orders, the page displays \u201cYou have no past orders.\u201d<\/li>\n<li>Orders older than 6 months are not shown by default.<\/li>\n<li>Clicking an order redirects me to a details page with line items and shipping address.<\/li>\n<\/ul>\n<p>This version is now testable. A QA engineer can write a scenario. A developer can implement against clear conditions.<\/p>\n<h2>Designing Actionable Acceptance Criteria<\/h2>\n<p>Not all criteria are created equal. Some are vague. Some are redundant. The best ones are specific, measurable, and aligned with user value.<\/p>\n<p>Use this checklist when writing acceptance criteria:<\/p>\n<ul>\n<li><strong>Start with the user:<\/strong> Every criterion should reflect a user-facing behavior.<\/li>\n<li><strong>Use Given-When-Then:<\/strong> This format forces clarity. <em>Given I\u2019m on the order page, when I click \u201cShow All\u201d, then I see all 50 orders.<\/em><\/li>\n<li><strong>Include edge cases:<\/strong> What if there are zero orders? What if the API fails?<\/li>\n<li><strong>Make it executable:<\/strong> Can a test be written based on this? If not, rewrite it.<\/li>\n<li><strong>Keep it concise:<\/strong> More than 5 criteria often mean the story is too broad.<\/li>\n<\/ul>\n<p>Ask yourself: \u201cCould someone not on the team understand this and verify it?\u201d If not, it\u2019s not testable.<\/p>\n<h3>Common Failure Patterns<\/h3>\n<p>Here are the most frequent mistakes I\u2019ve seen:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Problem<\/th>\n<th>Fix<\/th>\n<\/tr>\n<tr>\n<td>\u201cThe system should work.\u201d<\/td>\n<td>Replace with: \u201cWhen I submit the form, the confirmation message appears within 2 seconds.\u201d<\/td>\n<\/tr>\n<tr>\n<td>Criteria defined only in the PO\u2019s head.<\/td>\n<td>Write them down. Even if incomplete, get them on the board.<\/td>\n<\/tr>\n<tr>\n<td>Acceptance criteria written as tasks.<\/td>\n<td>Reframe: \u201cImplement authentication\u201d \u2192 \u201cWhen I\u2019m logged in, I see the dashboard.\u201d<\/td>\n<\/tr>\n<tr>\n<td>Only positive scenarios.<\/td>\n<td>Add: \u201cIf the API is down, show a user-friendly error message.\u201d<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Linking Acceptance Criteria to Definition of Done<\/h2>\n<p>Definition of done is not a checklist \u2014 it\u2019s a team agreement. But it only works when tied to real acceptance rules.<\/p>\n<p>Here\u2019s a practical pattern:<\/p>\n<ol>\n<li>Define acceptance criteria during refinement.<\/li>\n<li>Verify each criterion during testing.<\/li>\n<li>Only mark story as \u201cdone\u201d when all criteria pass.<\/li>\n<li>Update the Definition of Done to reflect this.<\/li>\n<\/ol>\n<p>Example:<\/p>\n<p>My team\u2019s DoD now includes:<\/p>\n<ul>\n<li>All acceptance criteria have been validated.<\/li>\n<li>Automated tests pass for all positive and negative scenarios.<\/li>\n<li>No known bugs in the acceptance test suite.<\/li>\n<\/ul>\n<p>This prevents the \u201cI thought it was working\u201d trap.<\/p>\n<h2>When to Stop: The Minimum Viable Acceptance Criteria<\/h2>\n<p>Just because a story is testable doesn\u2019t mean you need 20 criteria. You want the minimum that ensures value delivery.<\/p>\n<p>Ask: \u201cWhat is the simplest thing that could possibly work?\u201d<\/p>\n<p>For a login screen, the minimal testable definition might be:<\/p>\n<ul>\n<li>When I enter a valid email and password, I\u2019m redirected to the dashboard.<\/li>\n<li>When I enter invalid credentials, an error message appears.<\/li>\n<li>When I click \u201cForgot password?\u201d, I\u2019m taken to the reset page.<\/li>\n<\/ul>\n<p>That\u2019s enough for a working feature. Add more as needed.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I know when I\u2019ve written enough acceptance criteria?<\/h3>\n<p>When the story can be tested by someone not on the team who understands the user\u2019s goal. If you\u2019re still asking \u201cwhat does this mean?\u201d, keep refining.<\/p>\n<h3>Can acceptance criteria be written by the developer?<\/h3>\n<p>Not alone. They can help draft them, but acceptance criteria must emerge from collaboration between PO, dev, and QA. The goal is shared understanding.<\/p>\n<h3>What if the PO doesn\u2019t know what the criteria should be?<\/h3>\n<p>That\u2019s a red flag. The PO should work with users or stakeholders to define success. Use workshops or user interviews to clarify expectations. Acceptance criteria are not technical specs \u2014 they\u2019re value specs.<\/p>\n<h3>Do acceptance criteria replace technical acceptance tests?<\/h3>\n<p>No. Acceptance criteria define *what* the system should do. Technical tests (unit, integration) verify *how* it\u2019s built. Both are needed. But acceptance criteria define the boundary of value.<\/p>\n<h3>How do I handle changing acceptance criteria mid-sprint?<\/h3>\n<p>It\u2019s rare, but if it happens, discuss it in the sprint review. The story should be re-evaluated. If changes exceed scope, split or defer. The team must agree.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Stories are meant to [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":676,"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":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","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-680","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>Missing Acceptance Criteria: A Critical Agile Pitfall<\/title>\n<meta name=\"description\" content=\"Discover how missing acceptance criteria undermines Agile delivery. Learn how to define testable story definitions and avoid definition of done issues with real-world patterns and practices.\" \/>\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\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/missing-acceptance-criteria-agile\/\" \/>\n<meta property=\"og:locale\" content=\"zh_TW\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Missing Acceptance Criteria: A Critical Agile Pitfall\" \/>\n<meta property=\"og:description\" content=\"Discover how missing acceptance criteria undermines Agile delivery. Learn how to define testable story definitions and avoid definition of done issues with real-world patterns and practices.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/missing-acceptance-criteria-agile\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:13:52+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9810\u4f30\u95b1\u8b80\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 \u5206\u9418\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/missing-acceptance-criteria-agile\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/missing-acceptance-criteria-agile\/\",\"name\":\"Missing Acceptance Criteria: A Critical Agile Pitfall\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#website\"},\"datePublished\":\"2026-02-25T10:22:45+00:00\",\"dateModified\":\"2026-03-02T09:13:52+00:00\",\"description\":\"Discover how missing acceptance criteria undermines Agile delivery. Learn how to define testable story definitions and avoid definition of done issues with real-world patterns and practices.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/missing-acceptance-criteria-agile\/#breadcrumb\"},\"inLanguage\":\"zh-TW\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/missing-acceptance-criteria-agile\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/missing-acceptance-criteria-agile\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Mistakes in Writing User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Process and Collaboration Pitfalls\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Ignoring Acceptance Criteria and Definition of Done\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/\",\"name\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/tw\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-TW\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#organization\",\"name\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-TW\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Missing Acceptance Criteria: A Critical Agile Pitfall","description":"Discover how missing acceptance criteria undermines Agile delivery. Learn how to define testable story definitions and avoid definition of done issues with real-world patterns and practices.","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\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/missing-acceptance-criteria-agile\/","og_locale":"zh_TW","og_type":"article","og_title":"Missing Acceptance Criteria: A Critical Agile Pitfall","og_description":"Discover how missing acceptance criteria undermines Agile delivery. Learn how to define testable story definitions and avoid definition of done issues with real-world patterns and practices.","og_url":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/missing-acceptance-criteria-agile\/","og_site_name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","article_modified_time":"2026-03-02T09:13:52+00:00","twitter_card":"summary_large_image","twitter_misc":{"\u9810\u4f30\u95b1\u8b80\u6642\u9593":"6 \u5206\u9418"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/missing-acceptance-criteria-agile\/","url":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/missing-acceptance-criteria-agile\/","name":"Missing Acceptance Criteria: A Critical Agile Pitfall","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#website"},"datePublished":"2026-02-25T10:22:45+00:00","dateModified":"2026-03-02T09:13:52+00:00","description":"Discover how missing acceptance criteria undermines Agile delivery. Learn how to define testable story definitions and avoid definition of done issues with real-world patterns and practices.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/missing-acceptance-criteria-agile\/#breadcrumb"},"inLanguage":"zh-TW","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/missing-acceptance-criteria-agile\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/missing-acceptance-criteria-agile\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/tw\/"},{"@type":"ListItem","position":2,"name":"Common Mistakes in Writing User Stories","item":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/"},{"@type":"ListItem","position":3,"name":"Process and Collaboration Pitfalls","item":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/"},{"@type":"ListItem","position":4,"name":"Ignoring Acceptance Criteria and Definition of Done"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#website","url":"https:\/\/skills.visual-paradigm.com\/tw\/","name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/tw\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-TW"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#organization","name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/tw\/","logo":{"@type":"ImageObject","inLanguage":"zh-TW","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/680","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/680\/revisions"}],"predecessor-version":[{"id":2430,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/680\/revisions\/2430"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/676"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/media?parent=680"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/doc_tag?post=680"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}