{"id":1094,"date":"2026-02-25T10:35:52","date_gmt":"2026-02-25T10:35:52","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-fundamentals\/user-story-misconceptions-debunked\/"},"modified":"2026-02-25T10:35:52","modified_gmt":"2026-02-25T10:35:52","slug":"user-story-misconceptions-debunked","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-fundamentals\/user-story-misconceptions-debunked\/","title":{"rendered":"Common Misunderstandings About User Stories"},"content":{"rendered":"<p>One of the most persistent challenges in Agile delivery is the gap between how user stories are intended to be used and how they\u2019re actually applied. I\u2019ve seen teams treat stories as specifications, skip collaboration, or over-engineer acceptance criteria\u2014all while claiming they\u2019re being Agile. These aren\u2019t just minor quirks; they\u2019re systemic user story misconceptions that erode trust and slow delivery.<\/p>\n<p>What\u2019s often missing is the understanding that a user story is not a contract. It\u2019s a conversation starter. It\u2019s a commitment to talk, not a document to be signed off. I\u2019ve worked with teams where stories were written in perfect grammar but never discussed\u2014leading to rework, misalignment, and frustration.<\/p>\n<p>Here, I share real, field-tested insights to clear up common myths. You\u2019ll learn how to stop treating stories as blueprints, how to rebuild trust through collaboration, and how to focus on value\u2014not form. This is not theory. It\u2019s what actually works in high-performing teams.<\/p>\n<h2>Myth 1: A User Story Is a Requirements Document<\/h2>\n<p>Many teams treat user stories as if they must contain every detail needed for development. They write long, technical descriptions, embed acceptance criteria in the story body, and expect no further discussion.<\/p>\n<p>This is a misstep. The story\u2019s purpose isn\u2019t to be complete\u2014it\u2019s to be a prompt for conversation. When a story is so detailed that no discussion is needed, you\u2019ve lost its core value.<\/p>\n<p>Consider this: if you can\u2019t explain the story in a 60-second conversation with a developer, it\u2019s too detailed. You\u2019ve crossed from collaboration into documentation.<\/p>\n<p>Real-world example: A fintech team once wrote a 500-word story about a payment reconciliation feature. It included field names, error codes, and integration points. During sprint planning, the dev team realized they didn\u2019t understand the business context. The story had to be scrapped and rewritten as a simple \u201cAs a finance manager, I want to reconcile daily transactions so I can detect discrepancies.\u201d<\/p>\n<p>Key takeaway: <strong>User story myths<\/strong> thrive when teams confuse clarity with completeness. Prioritize conversation over detail.<\/p>\n<h3>When to Use Detailed Acceptance Criteria<\/h3>\n<p>Acceptance criteria should be just enough to guide discussion\u2014not to replace it. They\u2019re not a substitute for team conversation, but a shared reference point.<\/p>\n<ul>\n<li>Write acceptance criteria in simple, testable language.<\/li>\n<li>Use Given-When-Then format to model scenarios.<\/li>\n<li>Keep them short\u2014typically 3\u20135 points per story.<\/li>\n<\/ul>\n<h2>Myth 2: Stories Should Be Written in Isolation<\/h2>\n<p>I\u2019ve seen teams write user stories in isolation, then hand them off to developers with no follow-up. The story is \u201cdone\u201d once it\u2019s in the backlog.<\/p>\n<p>That\u2019s a red flag. The entire point of a user story is to create shared understanding through collaboration. Writing in isolation kills the conversation.<\/p>\n<p>Agile story misunderstandings often stem from this. Teams assume the story is \u201ccomplete\u201d when it\u2019s just written. But a story isn\u2019t a task\u2014it\u2019s a shared artifact.<\/p>\n<p>Best practice: co-write stories with developers, testers, and product owners. Use workshops to explore edge cases, clarify value, and align on outcomes.<\/p>\n<p>At a healthcare platform, we used a \u201cstory triage\u201d session before sprint planning. Three roles\u2014PO, dev, QA\u2014sat together to refine each story. What started as a vague idea became a well-understood item in under 15 minutes. The result? Zero last-minute scope changes.<\/p>\n<h3>Collaborative Story Writing: A 3-Step Process<\/h3>\n<ol>\n<li><strong>Start with the value<\/strong>: Ask, \u201cWho benefits? How? Why now?\u201d<\/li>\n<li><strong>Sketch the flow<\/strong>: Use a whiteboard to map high-level user steps.<\/li>\n<li><strong>Confirm the acceptance<\/strong>: Define 1\u20133 testable conditions.<\/li>\n<\/ol>\n<h2>Myth 3: Acceptance Criteria Replace the Conversation<\/h2>\n<p>Stories without conversation are just tickets. Acceptance criteria are not a replacement\u2014they\u2019re a supplement.<\/p>\n<p>Teams that rely solely on acceptance criteria often miss critical context. For example, a story about \u201cemail notifications\u201d might have criteria for delivery time and format, but not the emotional impact: \u201cUsers should feel confident they haven\u2019t missed important updates.\u201d<\/p>\n<p>I once worked with a team that delivered a feature with perfect acceptance criteria\u2014yet users still complained. Why? The team hadn\u2019t discussed usability, tone, or timing. The criteria were technically correct but emotionally irrelevant.<\/p>\n<p>Acceptance criteria should answer: \u201cHow do we know this works?\u201d Not \u201cWhat does it do?\u201d<\/p>\n<p>Use this checklist to ensure your criteria are meaningful:<\/p>\n<ul>\n<li>Are they written in plain language?<\/li>\n<li>Do they reflect user needs, not just system behavior?<\/li>\n<li>Can they be tested by someone without technical training?<\/li>\n<\/ul>\n<h2>Myth 4: All Stories Must Be Small<\/h2>\n<p>Yes, stories should be small. But not all stories are meant to be small. It\u2019s a myth that every story must fit in a sprint.<\/p>\n<p>Epics and large initiatives are real. The key is not to split them prematurely, but to use them to guide strategy and alignment.<\/p>\n<p>When teams force every story into a 1\u20133 day sprint, they often lose sight of the bigger picture. The story becomes a task, not a value driver.<\/p>\n<p>Best practice: use epics for strategic themes. Break them down only when you\u2019re ready to deliver. Use story mapping to visualize the flow.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Story Type<\/th>\n<th>Size<\/th>\n<th>When to Use<\/th>\n<\/tr>\n<tr>\n<td>User Story<\/td>\n<td>1\u20133 days<\/td>\n<td>High-value, deliverable feature<\/td>\n<\/tr>\n<tr>\n<td>Epic<\/td>\n<td>2\u20136 weeks<\/td>\n<td>Strategic initiative with multiple stories<\/td>\n<\/tr>\n<tr>\n<td>Feature<\/td>\n<td>1\u20132 sprints<\/td>\n<td>Group of related stories with shared outcome<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Myth 5: Stories Must Be Written by the Product Owner<\/h2>\n<p>While the product owner owns the backlog, writing stories is not a solo task. In fact, it\u2019s one of the most collaborative parts of Agile.<\/p>\n<p>Technical leads, UX designers, and QA specialists bring crucial context. A story written without their input often misses edge cases or usability concerns.<\/p>\n<p>At a SaaS company, we introduced \u201cco-writing sprints\u201d where POs, devs, and testers met weekly to refine the top 10 stories. Within two months, sprint completion rate rose from 65% to 88%. Why? The stories were clearer, less ambiguous, and better aligned with real user needs.<\/p>\n<p>Remember: a story is not a document\u2014it\u2019s a shared understanding. If only one person understands it, the team is already at risk.<\/p>\n<h2>Myth 6: Stories Are Not Needed in Lean or MVP Development<\/h2>\n<p>Some argue that in fast-moving startups or MVPs, stories slow things down. But the opposite is true.<\/p>\n<p>Without user stories, teams build features in isolation. They don\u2019t know who they\u2019re building for, why it matters, or how to test it. This leads to wasted effort and scope creep.<\/p>\n<p>Even in MVPs, user stories help prioritize. They force teams to ask: \u201cWhat\u2019s the smallest thing that delivers real value?\u201d<\/p>\n<p>An MVP is not a \u201cno-story\u201d project. It\u2019s a focused story exercise. Use the \u201cMinimum Valuable Story\u201d framework: start with the most critical user need, validate it, and iterate.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Can a user story be too short?<\/h3>\n<p>Yes. A story like \u201cAs a user, I want login\u201d lacks context and value. It\u2019s not testable. A good story must state a clear benefit. \u201cAs a user, I want to log in to access my dashboard so I can check my balance.\u201d<\/p>\n<h3>Should acceptance criteria be part of the user story?<\/h3>\n<p>No. Acceptance criteria should be separate. They\u2019re a tool for testing, not part of the story\u2019s narrative. Keep the story clean and focused on value.<\/p>\n<h3>How do I handle conflicting stakeholder views on a story?<\/h3>\n<p>Use the story as a collaboration trigger. Bring stakeholders together. Ask: \u201cWhat\u2019s the real goal?\u201d \u201cWho benefits?\u201d \u201cWhat outcome matters most?\u201d Often, the conflict resolves into alignment.<\/p>\n<h3>Is it okay to write stories in a backlog without refinement?<\/h3>\n<p>No. Unrefined stories are risky. They lack clarity and acceptance criteria. Use refinement sessions to ensure stories are ready for sprint planning.<\/p>\n<h3>What if my team insists on writing stories in full technical detail?<\/h3>\n<p>Reinforce that technical detail belongs in design docs or code\u2014not in the user story. The story is about people, not systems. Push back gently with: \u201cWould a user understand this?\u201d If not, rewrite.<\/p>\n<h3>Can user stories ever be replaced with other models?<\/h3>\n<p>Not entirely. User stories are not a replacement for modeling\u2014they\u2019re a complement. Use diagrams like story maps, personas, and workflows to deepen understanding. But always anchor back to the story: \u201cWho is this for? Why?\u201d<\/p>\n","protected":false},"excerpt":{"rendered":"<p>One of the most persistent challenges in Agile delivery is the gap between how user stories are intended to be [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1089,"menu_order":4,"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-1094","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 Misconceptions Debunked<\/title>\n<meta name=\"description\" content=\"Debunk common user story myths and agile story misunderstandings. Learn how to avoid pitfalls and improve collaboration with actionable insights from a 20-year Agile veteran.\" \/>\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\/user-story-fundamentals\/user-story-misconceptions-debunked\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"User Story Misconceptions Debunked\" \/>\n<meta property=\"og:description\" content=\"Debunk common user story myths and agile story misunderstandings. Learn how to avoid pitfalls and improve collaboration with actionable insights from a 20-year Agile veteran.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-fundamentals\/user-story-misconceptions-debunked\/\" \/>\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\/user-story-fundamentals\/user-story-misconceptions-debunked\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-fundamentals\/user-story-misconceptions-debunked\/\",\"name\":\"User Story Misconceptions Debunked\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-02-25T10:35:52+00:00\",\"description\":\"Debunk common user story myths and agile story misunderstandings. Learn how to avoid pitfalls and improve collaboration with actionable insights from a 20-year Agile veteran.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-fundamentals\/user-story-misconceptions-debunked\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-fundamentals\/user-story-misconceptions-debunked\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-fundamentals\/user-story-misconceptions-debunked\/#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\":\"The Foundations of Effective User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-fundamentals\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Common Misunderstandings About User Stories\"}]},{\"@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":"User Story Misconceptions Debunked","description":"Debunk common user story myths and agile story misunderstandings. Learn how to avoid pitfalls and improve collaboration with actionable insights from a 20-year Agile veteran.","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\/user-story-fundamentals\/user-story-misconceptions-debunked\/","og_locale":"ja_JP","og_type":"article","og_title":"User Story Misconceptions Debunked","og_description":"Debunk common user story myths and agile story misunderstandings. Learn how to avoid pitfalls and improve collaboration with actionable insights from a 20-year Agile veteran.","og_url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-fundamentals\/user-story-misconceptions-debunked\/","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\/user-story-fundamentals\/user-story-misconceptions-debunked\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-fundamentals\/user-story-misconceptions-debunked\/","name":"User Story Misconceptions Debunked","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-02-25T10:35:52+00:00","description":"Debunk common user story myths and agile story misunderstandings. Learn how to avoid pitfalls and improve collaboration with actionable insights from a 20-year Agile veteran.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-fundamentals\/user-story-misconceptions-debunked\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-fundamentals\/user-story-misconceptions-debunked\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-fundamentals\/user-story-misconceptions-debunked\/#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":"The Foundations of Effective User Stories","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/how-to-write-effective-user-stories\/user-story-fundamentals\/"},{"@type":"ListItem","position":4,"name":"Common Misunderstandings About User Stories"}]},{"@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\/1094","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\/1094\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/1089"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=1094"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=1094"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}