{"id":695,"date":"2026-02-25T10:22:52","date_gmt":"2026-02-25T10:22:52","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-checklist-diagnosis\/"},"modified":"2026-02-25T10:22:52","modified_gmt":"2026-02-25T10:22:52","slug":"user-story-checklist-diagnosis","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-checklist-diagnosis\/","title":{"rendered":"Diagnosing a Broken Story: A Step-by-Step Checklist"},"content":{"rendered":"

Every user story is a promise\u2014of clarity, value, and testability. But too many teams treat story writing as a formality, not a gateway to shared understanding. The real cost of a broken story isn\u2019t just in rework\u2014it\u2019s in wasted time, misaligned efforts, and stories that never deliver.<\/p>\n

I\u2019ve seen teams spend hours refining a story that, once tested, revealed a fundamental misunderstanding of the user\u2019s need. Not because the developers were wrong, but because the story itself was poorly defined from the start. That\u2019s where a structured diagnosis becomes essential.<\/p>\n

My experience has taught me: a story is never \u201cdone\u201d until it\u2019s been evaluated. A story that passes the checklist isn\u2019t necessarily good\u2014but one that fails should never be accepted as ready for development.<\/p>\n

This chapter gives you a repeatable, field-tested story evaluation framework. It\u2019s not about perfection. It\u2019s about catching flaws early, before the team invests time. You\u2019ll learn how to diagnose a broken story step by step, classify the issue, and decide the right path forward\u2014whether to revise, split, or reject.<\/p>\n

Why a Diagnosis Framework Is Non-Negotiable<\/h2>\n

Without a diagnostic process, teams fall into the trap of treating every story as valid simply because it\u2019s written. That\u2019s not quality\u2014it\u2019s compliance.<\/p>\n

Consider this: a story like \u201cThe system must save data\u201d sounds fine. But it lacks a user, a purpose, and any testable condition. It\u2019s technically a story, but functionally, it\u2019s a placeholder for confusion.<\/p>\n

That\u2019s why every story, regardless of how it was written, must be evaluated. A story quality checklist isn\u2019t a gate\u2014 it\u2019s a mirror. It reflects where assumptions are hiding and where clarity is missing.<\/p>\n

Over the past 20 years, I\u2019ve seen teams that use this checklist go from 40% story rework to under 10% in just one sprint cycle. The difference? They stopped guessing. They started diagnosing.<\/p>\n

Step-by-Step Story Evaluation Framework<\/h2>\n

Use this step-by-step process to assess any user story. Go through each checkpoint. If a story fails any point, it needs work.<\/p>\n

    \n
  1. Is the user role clear and specific?<\/strong> Avoid \u201cuser\u201d or \u201csomeone.\u201d Use a concrete persona: \u201cAs a registered customer\u2026\u201d<\/li>\n
  2. Is the goal actionable and outcome-focused?<\/strong> The verb must describe a measurable action: \u201cI want to reset my password\u201d not \u201cI want the system to allow me to reset.\u201d<\/li>\n
  3. Does the \u201cso that\u201d clause explain user value?<\/strong> It must answer: Why does this matter to the user? If it doesn\u2019t, the story lacks purpose.<\/li>\n
  4. Is the story small enough for one sprint?<\/strong> If it requires more than one developer-week, it\u2019s too big. Split it.<\/li>\n
  5. Are acceptance criteria testable?<\/strong> Every condition must be verifiable: \u201cWhen I click submit, the system shows an error if the email is invalid.\u201d<\/li>\n
  6. Does it align with the product vision or roadmap?<\/strong> A story that doesn\u2019t serve the bigger picture is often a waste of effort.<\/li>\n<\/ol>\n

    When a story fails any of these six checkpoints, it\u2019s not a problem to ignore. It\u2019s a signal.<\/p>\n

    Classifying the Problem: What\u2019s Really Wrong?<\/h3>\n

    Not all broken stories are broken in the same way. Diagnosing them isn\u2019t just about fixing grammar or structure\u2014it\u2019s about understanding the root of the flaw.<\/p>\n

    Use this classification table to categorize the issue. It helps the team respond with the right action.<\/p>\n\n\n\n\n\n\n\n
    Issue Type<\/th>\nExample<\/th>\nFix Strategy<\/th>\n<\/tr>\n
    Vague role<\/td>\n\u00ab\u00a0As a user, I want to log in\u00a0\u00bb<\/td>\nSpecify the persona: \u00ab\u00a0As a returning customer, I want to log in with my email.\u00a0\u00bb<\/td>\n<\/tr>\n
    Missing value<\/td>\n\u00ab\u00a0As a user, I want to see a list\u00a0\u00bb<\/td>\nAdd \u201cso that I can find my recent orders\u201d<\/td>\n<\/tr>\n
    Too large<\/td>\n\u00ab\u00a0As a manager, I want the full HR system\u00a0\u00bb<\/td>\nSplit into smaller stories: \u201cI want to view employee details,\u201d \u201cI want to edit vacation balances,\u201d etc.<\/td>\n<\/tr>\n
    Untestable<\/td>\n\u00ab\u00a0As a user, I want the system to be fast\u00a0\u00bb<\/td>\nRephrase: \u201cAs a user, I want the dashboard to load in under 2 seconds so I can make decisions quickly.\u201d<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Classifying the flaw isn\u2019t just about labeling\u2014it\u2019s about training the team to recognize patterns. After a few weeks of consistent use, they\u2019ll spot bad stories before they\u2019re even written.<\/p>\n

    When to Revise, Split, or Reject<\/h3>\n

    Not every diagnosis leads to a rewrite. Sometimes the story is salvageable. Sometimes it\u2019s not.<\/p>\n

    Use this decision tree to determine the next step:<\/p>\n

      \n
    • If the role is unclear \u2192 Revise<\/strong> with a specific persona.<\/li>\n
    • If the goal is vague or too broad \u2192 Split<\/strong> into smaller, focused stories.<\/li>\n
    • If the value statement is missing \u2192 Revise<\/strong> with a clear \u201cso that\u201d clause.<\/li>\n
    • If acceptance criteria are ambiguous \u2192 Revise<\/strong> with concrete examples.<\/li>\n
    • If the story is a technical task disguised as a user story \u2192 Reject<\/strong> and move to the technical backlog.<\/li>\n
    • If the story doesn\u2019t align with the roadmap or business goal \u2192 Pause<\/strong> until clarified.<\/li>\n<\/ul>\n

      Remember: a story that fails the checklist isn\u2019t broken\u2014it\u2019s incomplete. And that\u2019s okay. The goal isn\u2019t to write perfectly on the first try. It\u2019s to catch the flaw early and fix it efficiently.<\/p>\n

      Integrating the Checklist into Your Workflow<\/h2>\n

      This framework isn\u2019t just for backlog refinement. It\u2019s a tool for daily standups, sprint planning, and retrospectives.<\/p>\n

      At the start of each refinement session, run a quick diagnostic on 3\u20135 top stories. Use a shared checklist on a whiteboard or digital tool. Assign a team member to verify each point.<\/p>\n

      Over time, teams begin to self-correct. They stop writing \u201cI want to save data\u201d and start asking: \u201cWho benefits? What\u2019s the outcome? How do we know it works?\u201d<\/p>\n

      One team I worked with adopted this process and reduced story rework by 65% within two sprints. Not because they wrote better\u2014because they caught more issues before development began.<\/p>\n

      Common Pitfalls in Diagnosis<\/h2>\n

      Even with a checklist, teams fall into traps.<\/p>\n

        \n
      • Over-relying on the checklist.<\/strong> The checklist is a tool, not a substitute for conversation. A story can pass all points but still fail in practice.<\/li>\n
      • Diagnosing alone.<\/strong> Diagnosis should be a team activity. One person\u2019s view of \u201cclear\u201d may differ from another\u2019s.<\/li>\n
      • Skipping the \u201cwhy\u201d behind the flaw.<\/strong> Knowing \u201cthe value is missing\u201d is useful. Knowing why it was missing\u2014because the team didn\u2019t talk to users\u2014is where real learning happens.<\/li>\n<\/ul>\n

        Always follow diagnosis with dialogue. Ask: \u201cWhy was this value not stated?\u201d \u201cWho decided this was the user\u2019s goal?\u201d The answers shape better habits.<\/p>\n

        Frequently Asked Questions<\/h2>\n

        How do I know if a story is too small?<\/h3>\n

        A story is too small if it takes less than a day to implement and doesn\u2019t deliver a visible user outcome. Small stories are okay, but if they don\u2019t add value or can\u2019t be tested independently, consider grouping them into a larger story.<\/p>\n

        Should I use the checklist for every story?<\/h3>\n

        Yes. Even simple stories benefit from a quick check. A pattern emerges over time: teams that don\u2019t diagnose early are more likely to face rework later.<\/p>\n

        Can I use this with technical spikes?<\/h3>\n

        No. Technical spikes are research tasks, not user stories. Use a different format: \u201cAs a developer, I want to investigate X so I can assess feasibility.\u201d But even then, assess for clarity and testability.<\/p>\n

        What if the checklist highlights issues in a story that\u2019s already in progress?<\/h3>\n

        Stop. Re-evaluate. If the story is already being developed and the flaw is critical, pause the work. Refine the story before continuing. It\u2019s better to fix early than to rework later.<\/p>\n

        How often should we run the story evaluation framework?<\/h3>\n

        Use it every time a story is proposed, refined, or moved to sprint planning. Make it part of your Definition of Ready.<\/p>\n

        Can this framework replace acceptance criteria?<\/h3>\n

        No. The checklist diagnoses the story\u2019s structure and intent. Acceptance criteria define how to test it. Both are needed\u2014complementary, not interchangeable.<\/p>\n

        Diagnosing a broken story isn\u2019t about blame. It\u2019s about building a culture where clarity is expected, and misunderstanding is addressed early. The user story checklist diagnosis is not a hurdle\u2014it\u2019s a habit.<\/p>\n

        With consistent use of a story evaluation framework and a story quality checklist, teams don\u2019t just write better stories\u2014they build trust, reduce waste, and deliver with confidence.<\/p>\n

        Start small. Pick one story. Apply the checklist. See what changes. Then do it again. The improvements compound. The clarity multiplies.<\/p>\n

        That\u2019s how you turn vague asks into actionable work. That\u2019s how you build products users actually want.<\/p>\n","protected":false},"excerpt":{"rendered":"

        Every user story is a promise\u2014of clarity, value, and testability. But too many teams treat story writing as a formality, not a gateway to shared understanding. The real cost of a broken story isn\u2019t just in rework\u2014it\u2019s in wasted time, misaligned efforts, and stories that never deliver. I\u2019ve seen teams spend hours refining a story […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":694,"menu_order":0,"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-695","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nUser Story Checklist Diagnosis<\/title>\n<meta name=\"description\" content=\"Use this story evaluation framework and story quality checklist to diagnose broken user stories, uncover hidden flaws, and improve Agile delivery with confidence.\" \/>\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\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-checklist-diagnosis\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"User Story Checklist Diagnosis\" \/>\n<meta property=\"og:description\" content=\"Use this story evaluation framework and story quality checklist to diagnose broken user stories, uncover hidden flaws, and improve Agile delivery with confidence.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-checklist-diagnosis\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Fran\u00e7ais\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-checklist-diagnosis\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-checklist-diagnosis\/\",\"name\":\"User Story Checklist Diagnosis\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:22:52+00:00\",\"description\":\"Use this story evaluation framework and story quality checklist to diagnose broken user stories, uncover hidden flaws, and improve Agile delivery with confidence.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-checklist-diagnosis\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-checklist-diagnosis\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-checklist-diagnosis\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Mistakes in Writing User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Fixing Bad Stories: Patterns and Remedies\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Diagnosing a Broken Story: A Step-by-Step Checklist\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Fran\u00e7ais\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"User Story Checklist Diagnosis","description":"Use this story evaluation framework and story quality checklist to diagnose broken user stories, uncover hidden flaws, and improve Agile delivery with confidence.","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\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-checklist-diagnosis\/","og_locale":"fr_FR","og_type":"article","og_title":"User Story Checklist Diagnosis","og_description":"Use this story evaluation framework and story quality checklist to diagnose broken user stories, uncover hidden flaws, and improve Agile delivery with confidence.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-checklist-diagnosis\/","og_site_name":"Visual Paradigm Skills Fran\u00e7ais","twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-checklist-diagnosis\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-checklist-diagnosis\/","name":"User Story Checklist Diagnosis","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:22:52+00:00","description":"Use this story evaluation framework and story quality checklist to diagnose broken user stories, uncover hidden flaws, and improve Agile delivery with confidence.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-checklist-diagnosis\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-checklist-diagnosis\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/user-story-checklist-diagnosis\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"Common Mistakes in Writing User Stories","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/"},{"@type":"ListItem","position":3,"name":"Fixing Bad Stories: Patterns and Remedies","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/"},{"@type":"ListItem","position":4,"name":"Diagnosing a Broken Story: A Step-by-Step Checklist"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website","url":"https:\/\/skills.visual-paradigm.com\/fr\/","name":"Visual Paradigm Skills Fran\u00e7ais","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization","name":"Visual Paradigm Skills Fran\u00e7ais","url":"https:\/\/skills.visual-paradigm.com\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Fran\u00e7ais"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/695","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/695\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/694"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=695"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=695"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}