{"id":784,"date":"2026-02-25T10:24:33","date_gmt":"2026-02-25T10:24:33","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-in-agile-development-lightweight-modeling\/"},"modified":"2026-02-25T10:24:33","modified_gmt":"2026-02-25T10:24:33","slug":"crc-in-agile-development-lightweight-modeling","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-in-agile-development-lightweight-modeling\/","title":{"rendered":"CRC Meets Agile: Lightweight Modeling for Iterative Design"},"content":{"rendered":"<p>Agile teams often face a challenge: how to design quickly without sacrificing clarity. I\u2019ve seen dozens of teams struggle with oversized user stories, unclear responsibilities, or architectural drift\u2014all before writing a single line of code. The solution? Not more documentation. Not complex diagrams. Just a simple, shared conversation using CRC cards.<\/p>\n<p>When I first introduced CRC in agile retrospectives, the feedback was always the same: \u201cThis feels too lightweight.\u201d But after a few sessions, the shift became visible\u2014teams stopped arguing over class names and started discussing responsibilities. That\u2019s the power of CRC in agile development: it makes design tangible, collaborative, and rapid.<\/p>\n<p>This chapter shows how to embed CRC modeling into your sprint workflow\u2014not as a separate phase, but as a natural companion to story refinement, spike sessions, and design spikes. You\u2019ll learn how to use CRC for user stories, decompose complex features, and validate design choices in real time, all while staying true to agile principles.<\/p>\n<h2>Why CRC Fits Agile Like a Glove<\/h2>\n<p>Agile thrives on collaboration, adaptability, and small, frequent deliveries. CRC modeling aligns perfectly with these values. It\u2019s lightweight, visual, and encourages team dialogue\u2014exactly what agile needs during planning and refinement.<\/p>\n<p>Unlike heavyweight UML diagrams that lag behind, CRC cards are built for speed. You can sketch them on a whiteboard in minutes, reshuffle them when requirements shift, and keep them in sync with your backlog.<\/p>\n<p>Teams that integrate CRC in agile development report fewer misunderstandings, faster story breakdowns, and earlier detection of design flaws\u2014all without slowing down.<\/p>\n<h3>Key Benefits of CRC in Agile<\/h3>\n<ul>\n<li><strong>Speed to insight:<\/strong> A 10-minute session can clarify responsibilities that might take hours in traditional design meetings.<\/li>\n<li><strong>Shared ownership:<\/strong> Everyone\u2014devs, testers, product owners\u2014contributes equally to the model.<\/li>\n<li><strong>Adaptability:<\/strong> Cards can be updated instantly when a story changes or a new requirement emerges.<\/li>\n<li><strong>Early validation:<\/strong> You catch coupling issues or missing responsibilities before implementation begins.<\/li>\n<\/ul>\n<h2>How to Use CRC for User Stories: A Practical Workflow<\/h2>\n<p>Every user story is a promise. But that promise only holds if the team knows what it takes to fulfill it. CRC cards turn vague intent into concrete, testable design.<\/p>\n<p>Here\u2019s how to use <strong>agile modeling CRC<\/strong> during story refinement:<\/p>\n<ol>\n<li><strong>Start with a user story.<\/strong> For example: \u201cAs a customer, I want to cancel my subscription so I don\u2019t get charged again.\u201d<\/li>\n<li><strong>Identify key classes.<\/strong> Brainstorm: <code>Customer<\/code>, <code>Subscription<\/code>, <code>PaymentProcessor<\/code>, <code>NotificationService<\/code>.<\/li>\n<li><strong>Assign responsibilities.<\/strong> For each class, define what it does. For <code>Subscription<\/code>, responsibilities might include \u201ccheck if cancellation is allowed\u201d and \u201cupdate status to canceled.\u201d<\/li>\n<li><strong>Define collaborations.<\/strong> Who talks to whom? \u201cSubscription\u201d might collaborate with \u201cPaymentProcessor\u201d to issue a refund.<\/li>\n<li><strong>Review for gaps.<\/strong> Does anything seem missing? Maybe a <code>SubscriptionCancellationRequest<\/code> class is needed to track the process.<\/li>\n<\/ol>\n<p>This process takes 10\u201315 minutes per story and surfaces critical design decisions early. It turns a story from \u201cI want to cancel\u201d into \u201cHere\u2019s how we cancel, and what happens after.\u201d<\/p>\n<h3>Example: CRC for a User Story<\/h3>\n<p><strong>Story:<\/strong> \u201cThe system must notify users when their subscription ends.\u201d<\/p>\n<table>\n<tbody>\n<tr>\n<th>Class<\/th>\n<th>Responsibilities<\/th>\n<th>Collaborators<\/th>\n<\/tr>\n<tr>\n<td><code>Subscription<\/code><\/td>\n<td>Check end date<\/td>\n<td><code>NotificationService<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>NotificationService<\/code><\/td>\n<td>Send email reminder<\/td>\n<td><code>Customer<\/code>, <code>Subscription<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>Customer<\/code><\/td>\n<td>Receive notifications<\/td>\n<td><code>NotificationService<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This simple model reveals dependencies and responsibilities that might have been missed in verbal discussion.<\/p>\n<h2>Iterative CRC: Evolving Design Across Sprints<\/h2>\n<p>Agile teams don\u2019t design once. They refine constantly. <strong>iterative CRC<\/strong> supports this by allowing you to revisit and update models each sprint.<\/p>\n<p>When a story is completed, review the CRC model. Did you miss anything? Did a dependency grow? Add new cards or adjust responsibilities to reflect what you\u2019ve learned.<\/p>\n<p>For example, after implementing a refund system, you might realize that <code>PaymentProcessor<\/code> needs a new responsibility: \u201ctrack refund status.\u201d That update becomes part of the next story\u2019s design.<\/p>\n<h3>Best Practices for Iterative CRC<\/h3>\n<ul>\n<li><strong>Keep it visible:<\/strong> Use a whiteboard or digital tool like Visual Paradigm to maintain continuity across sprints.<\/li>\n<li><strong>Update after each spike:<\/strong> A spike often reveals new classes or responsibilities. Update the model immediately.<\/li>\n<li><strong>Pair with acceptance criteria:<\/strong> Use the CRC model to validate that a story\u2019s acceptance tests cover all responsibilities.<\/li>\n<li><strong>Archive old models:<\/strong> Keep historical versions to see how design evolved\u2014useful for retrospectives.<\/li>\n<\/ul>\n<h2>Overcoming Common Challenges<\/h2>\n<p>Even with their simplicity, teams sometimes struggle with CRC in agile. Here are real issues and how to fix them.<\/p>\n<h3>Problem: Too many classes<\/h3>\n<p>After a few sessions, some teams end up with 20+ classes for a single story. That\u2019s a red flag.<\/p>\n<p><strong>Solution:<\/strong> Ask: \u201cIs this class essential to fulfilling the story?\u201d If not, merge it with another or reconsider its role. Focus on core domain concepts, not every possible entity.<\/p>\n<h3>Problem: Vague responsibilities<\/h3>\n<p>Phrases like \u201chandle data\u201d or \u201cmanage payments\u201d don\u2019t guide implementation.<\/p>\n<p><strong>Solution:<\/strong> Reframe responsibilities as active verbs. \u201cProcess refund\u201d is better than \u201chandle refunds.\u201d Be specific: \u201cCalculate refund amount based on days left\u201d.<\/p>\n<h3>Problem: No one owns the model<\/h3>\n<p>Once the session ends, the cards are left behind.<\/p>\n<p><strong>Solution:<\/strong> Assign a rotating \u201cCRC steward\u201d per sprint. Their job: keep the model visible, update it after spikes, and share it in stand-ups.<\/p>\n<h2>From CRC to Code: Bridging the Gap<\/h2>\n<p>When it\u2019s time to code, the CRC model becomes a living blueprint. Each responsibility maps to a method. Each collaboration to a method call.<\/p>\n<p>For example, the responsibility \u201csend email reminder\u201d becomes a method like <code>sendEndOfSubscriptionReminder()<\/code> in the <code>NotificationService<\/code> class.<\/p>\n<p>This keeps the code aligned with the model. If a class has 8 responsibilities, it\u2019s a warning sign. Time to refactor.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Can CRC replace UML in agile?<\/h3>\n<p>No, but it complements it. CRC is ideal for initial modeling and team alignment. UML diagrams are better for documentation and complex relationships. Use CRC early, UML later.<\/p>\n<h3>How often should we update CRC models?<\/h3>\n<p>Update them whenever a story changes, a spike reveals new insights, or a new class emerges. Keep the model current\u2014don\u2019t wait for the next sprint.<\/p>\n<h3>Is CRC suitable for large teams?<\/h3>\n<p>Yes, but break it into smaller groups. Use CRC in parallel sessions for different features, then merge models during integration reviews.<\/p>\n<h3>What if my team disagrees on responsibilities?<\/h3>\n<p>That\u2019s normal. Use the model to debate. Ask: \u201cDoes this responsibility belong to this class?\u201d or \u201cCan this be simplified?\u201d Focus on cohesion, not consensus.<\/p>\n<h3>Can CRC be used for technical stories?<\/h3>\n<p>Absolutely. For a story like \u201cRefactor payment processing,\u201d CRC helps identify dependencies and test boundaries. It\u2019s not just for user-facing features.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Agile teams often face a challenge: how to design quick [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":782,"menu_order":1,"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-784","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>CRC in Agile Development: Lightweight Modeling<\/title>\n<meta name=\"description\" content=\"Learn how CRC in agile development supports story decomposition and iterative design with lightweight, collaborative modeling that keeps teams aligned and systems maintainable.\" \/>\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\/crc-cards-explained\/crc-beyond-coding\/crc-in-agile-development-lightweight-modeling\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"CRC in Agile Development: Lightweight Modeling\" \/>\n<meta property=\"og:description\" content=\"Learn how CRC in agile development supports story decomposition and iterative design with lightweight, collaborative modeling that keeps teams aligned and systems maintainable.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-in-agile-development-lightweight-modeling\/\" \/>\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=\"5 \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\/crc-cards-explained\/crc-beyond-coding\/crc-in-agile-development-lightweight-modeling\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-in-agile-development-lightweight-modeling\/\",\"name\":\"CRC in Agile Development: Lightweight Modeling\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:24:33+00:00\",\"description\":\"Learn how CRC in agile development supports story decomposition and iterative design with lightweight, collaborative modeling that keeps teams aligned and systems maintainable.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-in-agile-development-lightweight-modeling\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-in-agile-development-lightweight-modeling\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-in-agile-development-lightweight-modeling\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"CRC Cards Explained: A Beginner\u2019s Modeling Guide\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Applying CRC Thinking Beyond Software\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/crc-beyond-coding\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"CRC Meets Agile: Lightweight Modeling for Iterative Design\"}]},{\"@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":"CRC in Agile Development: Lightweight Modeling","description":"Learn how CRC in agile development supports story decomposition and iterative design with lightweight, collaborative modeling that keeps teams aligned and systems maintainable.","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\/crc-cards-explained\/crc-beyond-coding\/crc-in-agile-development-lightweight-modeling\/","og_locale":"zh_CN","og_type":"article","og_title":"CRC in Agile Development: Lightweight Modeling","og_description":"Learn how CRC in agile development supports story decomposition and iterative design with lightweight, collaborative modeling that keeps teams aligned and systems maintainable.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-in-agile-development-lightweight-modeling\/","og_site_name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4":"5 \u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-in-agile-development-lightweight-modeling\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-in-agile-development-lightweight-modeling\/","name":"CRC in Agile Development: Lightweight Modeling","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:24:33+00:00","description":"Learn how CRC in agile development supports story decomposition and iterative design with lightweight, collaborative modeling that keeps teams aligned and systems maintainable.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-in-agile-development-lightweight-modeling\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-in-agile-development-lightweight-modeling\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/crc-beyond-coding\/crc-in-agile-development-lightweight-modeling\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/cn\/"},{"@type":"ListItem","position":2,"name":"CRC Cards Explained: A Beginner\u2019s Modeling Guide","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/"},{"@type":"ListItem","position":3,"name":"Applying CRC Thinking Beyond Software","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-explained\/crc-beyond-coding\/"},{"@type":"ListItem","position":4,"name":"CRC Meets Agile: Lightweight Modeling for Iterative Design"}]},{"@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\/784","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\/784\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/782"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=784"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=784"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}