{"id":706,"date":"2026-02-25T10:22:57","date_gmt":"2026-02-25T10:22:57","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/sustainable-user-story-writing\/"},"modified":"2026-02-25T10:22:57","modified_gmt":"2026-02-25T10:22:57","slug":"sustainable-user-story-writing","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/sustainable-user-story-writing\/","title":{"rendered":"Conclusion: Writing Stories That Stand the Test of Change"},"content":{"rendered":"<p>Stories that only work today but collapse under tomorrow\u2019s changes are a silent drain on agility. I\u2019ve seen teams spend weeks refining a single story, only to see it invalidated by a minor shift in product direction or user needs. The real challenge isn\u2019t writing stories\u2014it\u2019s writing them so they outlive the sprint, the release, even the original team.<\/p>\n<p>What I\u2019ve learned over two decades is this: sustainable user story writing isn\u2019t about perfection. It\u2019s about *resilience*. It\u2019s about crafting stories that remain useful, testable, and understandable\u2014long after the first conversation ends.<\/p>\n<p>This chapter distills the essence of what works at scale. It\u2019s not about rigid rules, but about habits that evolve with your product and team. You\u2019ll walk away with actionable practices that prioritize adaptability, continuity, and real user value over short-term convenience.<\/p>\n<h2>Core Principles of Sustainable User Story Writing<\/h2>\n<h3>1. Focus on Value, Not Just Function<\/h3>\n<p>Every story must answer: \u201cWhy does this matter?\u201d If the outcome isn&#8217;t measurable or meaningful to a real user or business goal, it\u2019s not a story\u2014it\u2019s a task in disguise.<\/p>\n<p>Ask: \u201cWhat changes for the user when this is done?\u201d If the answer is vague or technical (\u201cthe system is faster\u201d), reframe it around observable outcomes like \u201cI can submit my tax form in less than 90 seconds\u201d or \u201cI can track my expenses without switching apps.\u201d<\/p>\n<p>Value-first stories resist scope creep. They stay relevant when priorities shift.<\/p>\n<h3>2. Build for Change, Not Just Completion<\/h3>\n<p>Good stories anticipate change. They\u2019re not written as static promises\u2014they\u2019re designed as open-ended invitations to conversation.<\/p>\n<p>Instead of locking down every detail, use placeholders like \u201cuser can view all payments from October 2024\u201d and tag it with a note: \u201cPending confirmation from finance team on date format.\u201d This keeps the story alive through feedback, even if the format changes.<\/p>\n<p>That\u2019s how you maintain adaptability: by embracing uncertainty as part of the process.<\/p>\n<h3>3. Use Adaptive Agile Stories as a Foundation<\/h3>\n<p>Agile isn\u2019t about doing the same thing every sprint. It\u2019s about responding to change. That means your stories must be written with flexibility in mind.<\/p>\n<p>Here\u2019s what makes a story adaptive:<\/p>\n<ul>\n<li>Phrased around user roles, not system features<\/li>\n<li>Includes a clear outcome, not just an action<\/li>\n<li>Leaves room for refinement as context emerges<\/li>\n<li>Uses acceptance criteria that can be updated, not overwritten<\/li>\n<\/ul>\n<p>These stories don\u2019t die when requirements shift. They grow.<\/p>\n<h3>4. Prioritize Long-Term Story Practices<\/h3>\n<p>Sustainable writing isn\u2019t a one-off fix. It\u2019s a rhythm. Teams that thrive implement long-term story practices that endure across releases.<\/p>\n<p>Consider these habits:<\/p>\n<ol>\n<li><strong>Regular backlog refinement<\/strong>\u2014Not just for sizing, but for clarity, context, and alignment.<\/li>\n<li><strong>Story health checks<\/strong>\u2014Review stories monthly for outdated assumptions, redundant logic, or missing context.<\/li>\n<li><strong>Versioning and traceability<\/strong>\u2014Link stories to their original intent, design decisions, and acceptance tests.<\/li>\n<li><strong>Shared understanding rituals<\/strong>\u2014Use story maps, visual models, and workshops to keep the team aligned.<\/li>\n<\/ol>\n<p>These aren\u2019t maintenance tasks. They\u2019re investments in future agility.<\/p>\n<h2>Practical Framework: The 4-Pillar Model for Long-Term Story Health<\/h2>\n<p>Here\u2019s a framework I\u2019ve used in teams across fintech, healthcare, and SaaS to ensure stories remain viable over time.<\/p>\n<table>\n<thead>\n<tr>\n<th>Pillar<\/th>\n<th>Why It Matters<\/th>\n<th>How to Apply<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Clarity<\/strong><\/td>\n<td>Prevents misinterpretation and rework<\/td>\n<td>Use plain language. Avoid jargon. Ensure any team member can read and understand it without context.<\/td>\n<\/tr>\n<tr>\n<td><strong>Context<\/strong><\/td>\n<td>Enables future teams to inherit the story<\/td>\n<td>Add a \u201cwhy\u201d note: link to roadmap, user interviews, or decision logs.<\/td>\n<\/tr>\n<tr>\n<td><strong>Testability<\/strong><\/td>\n<td>Ensures measurable outcomes<\/td>\n<td>Acceptance criteria must be verifiable. Use Given-When-Then format.<\/td>\n<\/tr>\n<tr>\n<td><strong>Adaptability<\/strong><\/td>\n<td>Allows evolution without rewriting<\/td>\n<td>Label stories with \u201copen to change\u201d or \u201cpending feedback\u201d if assumptions are untested.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Common Pitfalls in Long-Term Story Maintenance<\/h2>\n<p>Even well-written stories degrade over time. Here are the most frequent traps\u2014and how to avoid them:<\/p>\n<ul>\n<li><strong>Stale stories<\/strong>\u2014Stories that haven\u2019t been touched in 6+ months often become obsolete. Schedule a quarterly \u201cstory audit\u201d to prune or update them.<\/li>\n<li><strong>Overly technical language<\/strong>\u2014A story like \u201cImplement OAuth2.0 client credentials grant\u201d is not a user story. Reframe it as \u201cI want to log in via my company\u2019s SSO so I don\u2019t need a separate password.\u201d<\/li>\n<li><strong>Dependent on expired context<\/strong>\u2014Stories referencing \u201cthe new dashboard\u201d or \u201cthe feature from sprint 3\u201d lose value if the UI changes. Always reference functionality, not screens.<\/li>\n<li><strong>Missing acceptance criteria evolution<\/strong>\u2014Acceptance tests created at story start may not cover new edge cases. Revisit them during refinement.<\/li>\n<\/ul>\n<h2>Final Tips: How to Build a Sustainable Story Culture<\/h2>\n<p>It doesn\u2019t matter how good your writing is if the team doesn\u2019t value or maintain it. Here\u2019s how to make sustainable practices stick:<\/p>\n<ul>\n<li>Start retrospectives with a \u201cstory health\u201d check: \u201cWhat story was hard to understand? Why?\u201d<\/li>\n<li>Assign a \u201cstory steward\u201d per epic or feature to maintain clarity and context.<\/li>\n<li>Run \u201cstory rewriting\u201d workshops: Take old, broken stories and rebuild them as if they were new.<\/li>\n<li>Include story quality in your Definition of Done: \u201cAccepted by stakeholders\u201d is not enough\u2014\u201cUnderstood by developers and aligned with user value\u201d matters.<\/li>\n<\/ul>\n<p>Sustainable user story writing isn\u2019t about speed. It\u2019s about continuity. The best stories aren\u2019t those written perfectly\u2014they\u2019re the ones that last.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What does \u201csustainable user story writing\u201d really mean?<\/h3>\n<p>It means writing stories that remain clear, testable, and valuable\u2014not just during sprint planning, but through multiple releases, team changes, and evolving product goals. It\u2019s about designing for longevity, not just immediate delivery.<\/p>\n<h3>How do I know if my story is \u201cadaptive\u201d?<\/h3>\n<p>An adaptive story is one that doesn\u2019t rely on fixed assumptions. It includes open-ended language like \u201cpending confirmation,\u201d \u201csubject to feedback,\u201d or \u201cbased on current user needs.\u201d It\u2019s designed to be revisited and refined, not locked in at inception.<\/p>\n<h3>Can long-term story practices work in fast-moving startups?<\/h3>\n<p>Yes\u2014especially in startups, where product direction shifts often. Long-term practices help avoid rework and misaligned efforts. A well-maintained backlog becomes a competitive advantage, not a liability.<\/p>\n<h3>How often should I review older user stories?<\/h3>\n<p>At minimum, every quarter. Review stories that haven\u2019t been touched for over 6 months. Ask: \u201cIs this still valid? Is it still needed? Has context changed?\u201d Either update it, mark it as obsolete, or move it to a \u201cparking lot\u201d for future reference.<\/p>\n<h3>Do I need to create new stories when the user flow changes?<\/h3>\n<p>No\u2014but you should revise the existing story to reflect the new flow. Update the acceptance criteria, add new scenarios, and link to the new design. Never delete or ignore a story just because the flow evolved.<\/p>\n<h3>What if my team resists long-term story maintenance?<\/h3>\n<p>Start small. Pick one story per sprint to refactor and share with the team. Show how it reduced confusion or rework. Over time, the value becomes visible\u2014and the culture shifts. Lead by example, not mandate.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Stories that only work today but collapse under tomorrow\u2019s changes are a silent drain on agility. I\u2019ve seen teams spend weeks refining a single story, only to see it invalidated by a minor shift in product direction or user needs. The real challenge isn\u2019t writing stories\u2014it\u2019s writing them so they outlive the sprint, the release, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":701,"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-706","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>Sustainable User Story Writing for Agile Teams<\/title>\n<meta name=\"description\" content=\"Master sustainable user story writing techniques that ensure clarity, adaptability, and long-term value in Agile environments. Learn how to build stories that evolve with your product.\" \/>\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\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/sustainable-user-story-writing\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Sustainable User Story Writing for Agile Teams\" \/>\n<meta property=\"og:description\" content=\"Master sustainable user story writing techniques that ensure clarity, adaptability, and long-term value in Agile environments. Learn how to build stories that evolve with your product.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/sustainable-user-story-writing\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Espa\u00f1ol\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tiempo de lectura\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/sustainable-user-story-writing\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/sustainable-user-story-writing\/\",\"name\":\"Sustainable User Story Writing for Agile Teams\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\"},\"datePublished\":\"2026-02-25T10:22:57+00:00\",\"description\":\"Master sustainable user story writing techniques that ensure clarity, adaptability, and long-term value in Agile environments. Learn how to build stories that evolve with your product.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/sustainable-user-story-writing\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/sustainable-user-story-writing\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/sustainable-user-story-writing\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Mistakes in Writing User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Lessons Learned and Continuous Improvement\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Conclusion: Writing Stories That Stand the Test of Change\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/\",\"name\":\"Visual Paradigm Skills Espa\u00f1ol\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/es\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#organization\",\"name\":\"Visual Paradigm Skills Espa\u00f1ol\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Espa\u00f1ol\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Sustainable User Story Writing for Agile Teams","description":"Master sustainable user story writing techniques that ensure clarity, adaptability, and long-term value in Agile environments. Learn how to build stories that evolve with your product.","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\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/sustainable-user-story-writing\/","og_locale":"es_ES","og_type":"article","og_title":"Sustainable User Story Writing for Agile Teams","og_description":"Master sustainable user story writing techniques that ensure clarity, adaptability, and long-term value in Agile environments. Learn how to build stories that evolve with your product.","og_url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/sustainable-user-story-writing\/","og_site_name":"Visual Paradigm Skills Espa\u00f1ol","twitter_card":"summary_large_image","twitter_misc":{"Tiempo de lectura":"6 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/sustainable-user-story-writing\/","url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/sustainable-user-story-writing\/","name":"Sustainable User Story Writing for Agile Teams","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#website"},"datePublished":"2026-02-25T10:22:57+00:00","description":"Master sustainable user story writing techniques that ensure clarity, adaptability, and long-term value in Agile environments. Learn how to build stories that evolve with your product.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/sustainable-user-story-writing\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/sustainable-user-story-writing\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/sustainable-user-story-writing\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/es\/"},{"@type":"ListItem","position":2,"name":"Common Mistakes in Writing User Stories","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/"},{"@type":"ListItem","position":3,"name":"Lessons Learned and Continuous Improvement","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/"},{"@type":"ListItem","position":4,"name":"Conclusion: Writing Stories That Stand the Test of Change"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/es\/#website","url":"https:\/\/skills.visual-paradigm.com\/es\/","name":"Visual Paradigm Skills Espa\u00f1ol","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/es\/#organization","name":"Visual Paradigm Skills Espa\u00f1ol","url":"https:\/\/skills.visual-paradigm.com\/es\/","logo":{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Espa\u00f1ol"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/706","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/706\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/701"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media?parent=706"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/doc_tag?post=706"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}