{"id":674,"date":"2026-02-25T10:22:41","date_gmt":"2026-02-25T10:22:41","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/user-story-size-mistake\/"},"modified":"2026-02-25T10:22:41","modified_gmt":"2026-02-25T10:22:41","slug":"user-story-size-mistake","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/user-story-size-mistake\/","title":{"rendered":"Overly Broad or Tiny Stories"},"content":{"rendered":"<p>About 6 out of 10 teams I\u2019ve observed in the field struggle with story size \u2014 either writing stories that are too large to complete in a sprint or so small they don\u2019t deliver meaningful value. This imbalance isn\u2019t just a planning issue. It\u2019s a fundamental misstep in how Agile teams understand and deliver user value.<\/p>\n<p>Stories that are too broad often bundle multiple features or outcomes, making it hard to define acceptance criteria, estimate effort, or validate completion. They invite technical debt, misalignment, and rework. On the other hand, stories that are too tiny \u2014 like \u201cAdd a button\u201d \u2014 may be trivial to complete but offer no business or user value. They fragment work, clutter backlogs, and obscure the bigger picture.<\/p>\n<p>You\u2019ll learn how to diagnose whether a story is too big or too small, and most importantly, how to fix both issues using practical, field-tested techniques. You\u2019ll walk away with clear guidelines, decision points, and real examples of how to restructure stories for maximum clarity and impact.<\/p>\n<h2>Why Story Size Matters More Than You Think<\/h2>\n<p>Every story is a commitment to deliver value \u2014 not just a task to be checked off.<\/p>\n<p>Size directly affects planning accuracy, team morale, and sprint velocity. A story that takes 10 days to complete but is expected to be done in one sprint creates pressure, estimation bias, and constant firefighting.<\/p>\n<p>Conversely, a story so small it takes 15 minutes to build doesn\u2019t justify a full refinement session or a dedicated task. It becomes noise, diluting the backlog\u2019s signal-to-noise ratio.<\/p>\n<p>Size isn\u2019t just about effort \u2014 it\u2019s about value delivery. A story should deliver a visible, testable outcome that a real user can experience.<\/p>\n<h3>How to Spot a Problematic Story<\/h3>\n<p>Here\u2019s a quick diagnostic checklist:<\/p>\n<ul>\n<li>The story requires more than 3\u20135 days of work to complete<\/li>\n<li>It includes the word \u201cand\u201d or \u201cplus\u201d in the goal<\/li>\n<li>Acceptance criteria are impossible to define without assumptions<\/li>\n<li>It can\u2019t be tested independently without other stories<\/li>\n<li>It feels like a task disguised as a story<\/li>\n<\/ul>\n<p>If more than two of these apply, you\u2019ve likely got a user story size mistake on your hands.<\/p>\n<h2>Fixing Overly Broad Stories<\/h2>\n<p>Overly broad stories often stem from poor decomposition. A team might write: \u201cAs a customer, I want to manage my profile so that I can update my information.\u201d This seems simple \u2014 but it includes editing name, address, password, photo, and preferences.<\/p>\n<p>Such stories become untestable and unmanageable. They\u2019re a recipe for scope creep, missed commitments, and frustration.<\/p>\n<p>Here\u2019s how to break them down.<\/p>\n<h3>Strategy: Splitting User Stories by Value and Boundary<\/h3>\n<p>Use these two filters to split effectively:<\/p>\n<ol>\n<li><strong>By value delivery<\/strong> \u2013 Does the story deliver a distinct user benefit? If yes, keep it. If no, split.<\/li>\n<li><strong>By system boundary<\/strong> \u2013 Is the story tied to a single module or function? If not, split.<\/li>\n<\/ol>\n<p>Apply these rules to the example:<\/p>\n<ul>\n<li>As a customer, I want to update my name so that I can reflect my current identity.<\/li>\n<li>As a customer, I want to change my password so that my account stays secure.<\/li>\n<li>As a customer, I want to upload a profile photo so that I can personalize my account.<\/li>\n<\/ul>\n<p>Now each story delivers a specific, testable outcome. Each can be independently verified and estimated. The team can prioritize and deliver them in sequence.<\/p>\n<p>This is the essence of <strong>story granularity problems<\/strong>. Not all stories should be the same size \u2014 but none should be so large they block delivery.<\/p>\n<h3>When to Split: Decision Tree<\/h3>\n<p>Use this flow to decide whether a story needs splitting:<\/p>\n<ul>\n<li>Is the story longer than 3 days of work? \u2192 Split<\/li>\n<li>Does it involve more than one user role or system? \u2192 Split<\/li>\n<li>Can it be verified without the involvement of other stories? \u2192 Yes \u2192 Keep<\/li>\n<li>Does it have multiple \u201cso that\u201d outcomes? \u2192 Split<\/li>\n<\/ul>\n<p>Following this flow ensures you only split stories that are genuinely too big \u2014 not those that are just complex.<\/p>\n<h2>Fixing Overly Tiny Stories<\/h2>\n<p>Now consider this: \u201cAs a user, I want to click the submit button.\u201d<\/p>\n<p>It\u2019s technically a valid story. But it delivers no value. It doesn\u2019t meet a user need. It\u2019s just a UI task.<\/p>\n<p>These micro-stories clutter backlogs, inflate velocity, and distract from real value delivery.<\/p>\n<p>They often result from teams focusing on implementation instead of outcomes.<\/p>\n<h3>How to Identify and Fix Micro-Stories<\/h3>\n<p>Ask three questions:<\/p>\n<ol>\n<li>What does the user gain from this?<\/li>\n<li>Can this be tested without a larger context?<\/li>\n<li>Would a user notice this change?<\/li>\n<\/ol>\n<p>If the answer to any is \u201cno,\u201d it\u2019s a micro-story. Combine or rewrite it.<\/p>\n<p>Instead of \u201cAdd a button,\u201d try:<\/p>\n<ul>\n<li>As a user, I want to submit my form so that I can complete my registration.<\/li>\n<li>As a user, I want to confirm my email address so that I can activate my account.<\/li>\n<\/ul>\n<p>These are now stories with clear value, acceptance criteria, and testability.<\/p>\n<p>Remember: <strong>splitting user stories<\/strong> isn\u2019t about making them smaller \u2014 it\u2019s about making them meaningful.<\/p>\n<h3>Guidelines for Appropriate Story Granularity<\/h3>\n<p>Here\u2019s a practical guide to story size in story points:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Story Points<\/th>\n<th>Typical Story Size<\/th>\n<th>Recommended Use<\/th>\n<\/tr>\n<tr>\n<td>1<\/td>\n<td>Under 1 day of work<\/td>\n<td>Very small tasks (e.g., \u201cAdd a label\u201d) \u2014 only if tied to a larger value<\/td>\n<\/tr>\n<tr>\n<td>2\u20133<\/td>\n<td>1\u20132 days of work<\/td>\n<td>Small, testable features (e.g., \u201cUpdate email\u201d) \u2014 ideal<\/td>\n<\/tr>\n<tr>\n<td>5\u20138<\/td>\n<td>2\u20134 days of work<\/td>\n<td>Medium stories \u2014 can be split if too complex<\/td>\n<\/tr>\n<tr>\n<td>13+<\/td>\n<td>5+ days of work<\/td>\n<td>Must be split \u2014 indicates a user story size mistake<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Use this not as a rule, but as a reflection of your team\u2019s rhythm. If 8-point stories are common, you\u2019re likely under-splitting.<\/p>\n<h2>Practical Tips for Consistent Story Sizing<\/h2>\n<p>Size isn\u2019t arbitrary. It\u2019s a shared understanding refined through experience.<\/p>\n<ul>\n<li>Use a <strong>story size anchor<\/strong> \u2014 pick a 3-point story everyone agrees is \u201cabout right\u201d and compare others to it.<\/li>\n<li>Hold regular <strong>story size retrospectives<\/strong> \u2014 review 3\u20135 stories per sprint. Ask: \u201cWas the estimate accurate? Why or why not?\u201d<\/li>\n<li>Pair refinement with <strong>planning poker<\/strong> \u2014 but don\u2019t skip the conversation. The number is secondary to the discussion.<\/li>\n<li>Document your team\u2019s <strong>story size rules<\/strong> in your Definition of Ready. Include max size, minimum value, and splitting criteria.<\/li>\n<\/ul>\n<p>These practices build consistency and reduce the chance of repeating user story size mistakes.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I know if a story is too big to be in a sprint?<\/h3>\n<p>A story is too big if it exceeds your team\u2019s average sprint capacity. Most teams should avoid stories over 8 points. If a story takes more than 3\u20135 days to complete, split it.<\/p>\n<h3>Can I have a 1-point story?<\/h3>\n<p>Yes, but only if it delivers a real user value. A 1-point story should not be just a technical task. \u201cAdd a label\u201d isn\u2019t a story \u2014 \u201cAdd a confirmation label after submission\u201d is.<\/p>\n<h3>What if splitting a story breaks a technical dependency?<\/h3>\n<p>Don\u2019t let dependency block value delivery. Break the dependency during refinement, or deliver in phases. For example, split by feature layer: \u201cAdd input field,\u201d then \u201cValidate input,\u201d then \u201cSubmit form.\u201d This respects the flow of user experience.<\/p>\n<h3>Is there a standard for story size across teams?<\/h3>\n<p>No. Story size is relative to team velocity and context. A 5-point story for one team may be 8 points for another. Focus on consistency within your team, not across teams.<\/p>\n<h3>How often should I review story size in refinement?<\/h3>\n<p>Review story size in every refinement session. Use the size anchor and a checklist. If a story is over 8 points, it must be split before sprint planning.<\/p>\n<h3>Should I ever keep a story larger than 8 points?<\/h3>\n<p>Only if it\u2019s a known, well-understood epic that spans multiple sprints \u2014 and only after splitting it into smaller, value-delivering increments. Even then, it must be broken down during the sprint.<\/p>\n<p>Remember: a story is a placeholder for a conversation. But that conversation is pointless if the story is too big to discuss or too small to matter.<\/p>\n<p>Mastering story size isn\u2019t about guessing effort. It\u2019s about understanding user value, breaking down complexity, and building trust through transparency. When you fix the user story size mistake, you fix planning, delivery, and team alignment.<\/p>\n<p>Go back to your backlog. Find three stories that feel off. Apply the rules in this chapter. You\u2019ll see immediate improvements in clarity, team confidence, and delivery speed.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>About 6 out of 10 te [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":670,"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-674","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>User Story Size Mistake: Fixing Overly Broad or Tiny Stories<\/title>\n<meta name=\"description\" content=\"Stop wasting sprint time on poorly sized user stories. Learn how to fix splitting user stories and story granularity problems with proven techniques for better planning and team alignment.\" \/>\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\/user-story-structure-mistakes\/user-story-size-mistake\/\" \/>\n<meta property=\"og:locale\" content=\"zh_TW\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"User Story Size Mistake: Fixing Overly Broad or Tiny Stories\" \/>\n<meta property=\"og:description\" content=\"Stop wasting sprint time on poorly sized user stories. Learn how to fix splitting user stories and story granularity problems with proven techniques for better planning and team alignment.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/user-story-size-mistake\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\" \/>\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=\"7 \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\/user-story-structure-mistakes\/user-story-size-mistake\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/user-story-size-mistake\/\",\"name\":\"User Story Size Mistake: Fixing Overly Broad or Tiny Stories\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#website\"},\"datePublished\":\"2026-02-25T10:22:41+00:00\",\"description\":\"Stop wasting sprint time on poorly sized user stories. Learn how to fix splitting user stories and story granularity problems with proven techniques for better planning and team alignment.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/user-story-size-mistake\/#breadcrumb\"},\"inLanguage\":\"zh-TW\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/user-story-size-mistake\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/user-story-size-mistake\/#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\":\"Structural Mistakes That Undermine Clarity\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Overly Broad or Tiny Stories\"}]},{\"@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":"User Story Size Mistake: Fixing Overly Broad or Tiny Stories","description":"Stop wasting sprint time on poorly sized user stories. Learn how to fix splitting user stories and story granularity problems with proven techniques for better planning and team alignment.","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\/user-story-structure-mistakes\/user-story-size-mistake\/","og_locale":"zh_TW","og_type":"article","og_title":"User Story Size Mistake: Fixing Overly Broad or Tiny Stories","og_description":"Stop wasting sprint time on poorly sized user stories. Learn how to fix splitting user stories and story granularity problems with proven techniques for better planning and team alignment.","og_url":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/user-story-size-mistake\/","og_site_name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9810\u4f30\u95b1\u8b80\u6642\u9593":"7 \u5206\u9418"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/user-story-size-mistake\/","url":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/user-story-size-mistake\/","name":"User Story Size Mistake: Fixing Overly Broad or Tiny Stories","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#website"},"datePublished":"2026-02-25T10:22:41+00:00","description":"Stop wasting sprint time on poorly sized user stories. Learn how to fix splitting user stories and story granularity problems with proven techniques for better planning and team alignment.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/user-story-size-mistake\/#breadcrumb"},"inLanguage":"zh-TW","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/user-story-size-mistake\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/user-story-size-mistake\/#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":"Structural Mistakes That Undermine Clarity","item":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/"},{"@type":"ListItem","position":4,"name":"Overly Broad or Tiny Stories"}]},{"@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\/674","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":0,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/674\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/670"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/media?parent=674"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/doc_tag?post=674"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}