{"id":698,"date":"2026-02-25T10:22:54","date_gmt":"2026-02-25T10:22:54","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-review-techniques\/"},"modified":"2026-02-25T10:22:54","modified_gmt":"2026-02-25T10:22:54","slug":"user-story-review-techniques","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-review-techniques\/","title":{"rendered":"Story Review Techniques and Peer Feedback"},"content":{"rendered":"<p>Most teams believe they\u2019re reviewing stories correctly\u2014until they realize a sprint ends with half the backlog incomplete and developers questioning what was actually meant. The truth is, many reviews are just rubber-stamping. I\u2019ve seen teams go through five rounds of \u201cfeedback\u201d only to find the same story still lacks acceptance criteria. The real issue isn\u2019t people\u2014it\u2019s process.<\/p>\n<p>Here\u2019s the unvarnished truth: **a story review is not a quality gate\u2014it\u2019s a conversation trigger**. If your team waits for a review to catch problems, you\u2019re already behind. The best reviews happen *before* refinement, not after. They\u2019re built into the rhythm of collaboration, not a separate checkmark on a list.<\/p>\n<p>What you\u2019ll learn here isn\u2019t just another checklist. It\u2019s how to run peer review sessions that actually improve story quality, reduce rework, and build shared ownership. You\u2019ll walk away with proven formats, real examples, and a method to make story feedback feel productive\u2014not punitive.<\/p>\n<h2>Why Most Story Reviews Fail<\/h2>\n<p>Most story reviews fail not because people are careless, but because they\u2019re misaligned. A review meant to verify clarity ends up being a critique of writing style. Or worse, it becomes a chance to offload responsibility: \u201cI didn\u2019t write it, so I don\u2019t have to understand it.\u201d<\/p>\n<p>Even when teams use checklists, they often skip the most important part: **the why**. Why was this story written? What outcome are we trying to deliver? Without that, feedback is random, reactive, and rarely actionable.<\/p>\n<p>Here are the top four reasons peer review sessions collapse:<\/p>\n<ul>\n<li>Reviews happen too late\u2014after stories are already accepted into the sprint.<\/li>\n<li>Feedback is focused on grammar, not value or testability.<\/li>\n<li>Only one person leads the session\u2014others stay silent or disengage.<\/li>\n<li>No follow-up: issues are noted but never addressed.<\/li>\n<\/ul>\n<p>These aren\u2019t flaws in individuals. They\u2019re systemic. Fix the process, and the problems go away.<\/p>\n<h2>Effective Peer Review Techniques<\/h2>\n<h3>1. The 15-Minute Story Blitz<\/h3>\n<p>Speed builds focus. The 15-minute story blitz is a time-boxed peer review where each story gets exactly 90 seconds to be read aloud, followed by 30 seconds of rapid-fire feedback.<\/p>\n<p>Why it works: It prevents long-winded explanations and forces clarity. If you can\u2019t explain the story in 60 seconds, it\u2019s too complex. The 30 seconds of feedback are limited to one critical insight: \u201cMissing acceptance criteria,\u201d \u201cUnclear role,\u201d or \u201cToo broad\u2014split with subtasks.\u201d<\/p>\n<p>Best for: Sprint planning, backlog refinement, and onboarding new team members.<\/p>\n<h3>2. The Rubric-Driven Review<\/h3>\n<p>Use a simple scoring rubric to evaluate stories on key dimensions. This turns subjective feedback into measurable insight.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Criteria<\/th>\n<th>Score (1\u20135)<\/th>\n<th>Notes<\/th>\n<\/tr>\n<tr>\n<td>Clear user role<\/td>\n<td>[ ]<\/td>\n<td>Is the actor specific?<\/td>\n<\/tr>\n<tr>\n<td>Value-driven goal<\/td>\n<td>[ ]<\/td>\n<td>Does it answer \u201cso that\u201d?<\/td>\n<\/tr>\n<tr>\n<td>Testable acceptance<\/td>\n<td>[ ]<\/td>\n<td>Can we write a test from this?<\/td>\n<\/tr>\n<tr>\n<td>Appropriate size<\/td>\n<td>[ ]<\/td>\n<td>Can it be done in one sprint?<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>After scoring, discuss only the 3s and below. This focuses energy where it matters. I\u2019ve used this with teams across fintech, healthcare, and ed-tech\u2014always with faster alignment and fewer surprises at demo time.<\/p>\n<h3>3. The Two-Person Feedback Loop<\/h3>\n<p>Instead of group critiques, pair two team members to review one story. One person reads, the other takes notes using this framework:<\/p>\n<ul>\n<li><strong>Clarity<\/strong>: Can you explain this in your own words?<\/li>\n<li><strong>Testability<\/strong>: What would we need to test this?<\/li>\n<li><strong>Value<\/strong>: Who benefits? How?<\/li>\n<li><strong>Next Step<\/strong>: What\u2019s missing? What should we do?<\/li>\n<\/ul>\n<p>After 10 minutes, they present their findings to the larger team. This ensures every story gets deep attention, not just quick approval.<\/p>\n<h3>4. Story Feedback Process: A Repeatable Workflow<\/h3>\n<p>Here\u2019s how to structure your peer review user stories into a reliable cycle:<\/p>\n<ol>\n<li><strong>Assign reviewers<\/strong>: Not the author. Rotate roles weekly.<\/li>\n<li><strong>Read aloud<\/strong>: No silent reading. Verbalizing forces clarity.<\/li>\n<li><strong>Apply the rubric<\/strong>: Score each dimension. Mark only what\u2019s critical.<\/li>\n<li><strong>Ask one question<\/strong>: \u201cWhat\u2019s the one thing that would make this story better?\u201d<\/li>\n<li><strong>Update the story<\/strong>: The author revises it\u2014no debate, no delay.<\/li>\n<li><strong>Revalidate<\/strong>: If major changes, repeat steps 1\u20135.<\/li>\n<\/ol>\n<p>This process works because it\u2019s lightweight, repeatable, and focused. It doesn\u2019t replace collaboration\u2014it enhances it.<\/p>\n<h2>Common Pitfalls in Peer Review<\/h2>\n<p>Even with good intent, teams fall into traps. Be aware of these:<\/p>\n<ul>\n<li><strong>Feedback without follow-through<\/strong>: A comment like \u201cToo vague\u201d is useless unless paired with a suggestion: \u201cTry adding: \u2018so that I can compare prices across three providers.\u2019\u201d<\/li>\n<li><strong>Over-reliance on templates<\/strong>: A \u201cperfect\u201d story format doesn\u2019t guarantee value. The structure is a tool, not a rule.<\/li>\n<li><strong>Power dynamics<\/strong>: Senior members often dominate. Use anonymous input forms or digital tools to level the field.<\/li>\n<li><strong>Feedback that feels personal<\/strong>: \u201cThis is bad\u201d vs \u201cThis could be clearer if we rephrase the goal.\u201d Phrase feedback as improvement, not judgment.<\/li>\n<\/ul>\n<p>When feedback feels like criticism, the next story never gets improved. When it feels like support, teams grow.<\/p>\n<h2>Building a Sustainable Feedback Culture<\/h2>\n<p>Peer review isn\u2019t a one-off task. It\u2019s a muscle. The best teams don\u2019t wait for flaws\u2014they train their instincts.<\/p>\n<p>I\u2019ve seen teams where every member starts refinement with one sentence: \u201cI\u2019ll check for clarity, testability, and value.\u201d No special role. No hierarchy. Just shared responsibility.<\/p>\n<p>Make it a habit:<\/p>\n<ul>\n<li>Start every sprint planning with a 5-minute story review ritual.<\/li>\n<li>Keep a shared feedback log: \u201cLast week, 3 stories were rewritten due to unclear outcomes.\u201d<\/li>\n<li>Recognize good feedback: \u201cThanks for catching the missing acceptance criteria\u2014this saved us two days of rework.\u201d<\/li>\n<\/ul>\n<p>Over time, peer review stops being a chore and becomes a signal of team health.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How often should we conduct peer review user stories?<\/h3>\n<p>At minimum, every story should be reviewed before sprint commitment. For complex or high-risk features, conduct a second review after acceptance criteria are defined. Use the 15-minute blitz or two-person loop for 100% coverage.<\/p>\n<h3>What if the product owner disagrees with peer feedback?<\/h3>\n<p>Feedback isn\u2019t about agreement\u2014it\u2019s about clarity. If a story is ambiguous, the owner should clarify, not override. Use the \u201cwhy\u201d behind feedback to reframe: \u201cThis story lacks outcome. If we don\u2019t fix it, how will we know it\u2019s done?\u201d<\/p>\n<h3>Can technical team members give meaningful story feedback?<\/h3>\n<p>Absolutely. Developers often spot gaps in testability or scalability that product owners miss. The key is to frame feedback around user value, not technical detail. For example: \u201cThis story doesn\u2019t define how the system responds under load\u2014could that affect usability?\u201d<\/p>\n<h3>Should feedback be anonymous?<\/h3>\n<p>Only if your team struggles with hierarchy or fear. Anonymous input can surface issues, but it reduces accountability. Best practice: combine anonymous suggestions with public discussion.&nbsp;<\/p>\n<h3>How do we handle pushback from developers who say \u201cWe\u2019ll figure it out later\u201d?<\/h3>\n<p>That\u2019s a red flag. If the team doesn\u2019t understand the story, it\u2019s not ready. Refuse to accept \u201cwe\u2019ll figure it out\u201d as a valid acceptance. Every story must be testable *before* coding starts. If it\u2019s not, it\u2019s not a story\u2014it\u2019s a task.<\/p>\n<h3>What\u2019s the biggest mistake in the story feedback process?<\/h3>\n<p>Treating feedback as a deliverable instead of a conversation. The goal isn\u2019t to \u201ccomplete\u201d a checklist. It\u2019s to ensure the story is understood, testable, and valuable. If the conversation ends with \u201cApproved,\u201d but no one really understands it, the story is still broken.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most teams believe they\u2019re reviewing stories correctly\u2014 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":694,"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-698","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 Review Techniques That Work<\/title>\n<meta name=\"description\" content=\"Master effective user story review techniques with proven peer feedback processes that improve clarity, testability, and team alignment. Learn how to turn vague stories into actionable development work.\" \/>\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\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-review-techniques\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"User Story Review Techniques That Work\" \/>\n<meta property=\"og:description\" content=\"Master effective user story review techniques with proven peer feedback processes that improve clarity, testability, and team alignment. Learn how to turn vague stories into actionable development work.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-review-techniques\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 \u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-review-techniques\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-review-techniques\/\",\"name\":\"User Story Review Techniques That Work\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:22:54+00:00\",\"description\":\"Master effective user story review techniques with proven peer feedback processes that improve clarity, testability, and team alignment. Learn how to turn vague stories into actionable development work.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-review-techniques\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-review-techniques\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-review-techniques\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Mistakes in Writing User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Fixing Bad Stories: Patterns and Remedies\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Story Review Techniques and Peer Feedback\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-Hans\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-Hans\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"User Story Review Techniques That Work","description":"Master effective user story review techniques with proven peer feedback processes that improve clarity, testability, and team alignment. Learn how to turn vague stories into actionable development work.","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\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-review-techniques\/","og_locale":"zh_CN","og_type":"article","og_title":"User Story Review Techniques That Work","og_description":"Master effective user story review techniques with proven peer feedback processes that improve clarity, testability, and team alignment. Learn how to turn vague stories into actionable development work.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-review-techniques\/","og_site_name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4":"6 \u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-review-techniques\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-review-techniques\/","name":"User Story Review Techniques That Work","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:22:54+00:00","description":"Master effective user story review techniques with proven peer feedback processes that improve clarity, testability, and team alignment. Learn how to turn vague stories into actionable development work.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-review-techniques\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-review-techniques\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-review-techniques\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/cn\/"},{"@type":"ListItem","position":2,"name":"Common Mistakes in Writing User Stories","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/"},{"@type":"ListItem","position":3,"name":"Fixing Bad Stories: Patterns and Remedies","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/"},{"@type":"ListItem","position":4,"name":"Story Review Techniques and Peer Feedback"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website","url":"https:\/\/skills.visual-paradigm.com\/cn\/","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-Hans"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/cn\/","logo":{"@type":"ImageObject","inLanguage":"zh-Hans","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/698","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/698\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/694"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=698"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=698"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}