{"id":6360,"date":"2026-06-09T09:00:00","date_gmt":"2026-06-09T07:00:00","guid":{"rendered":"https:\/\/storiesonboard.com\/blog\/make-backlog-agent-ready"},"modified":"2026-06-09T09:00:00","modified_gmt":"2026-06-09T07:00:00","slug":"make-backlog-agent-ready","status":"publish","type":"post","link":"https:\/\/storiesonboard.com\/blog\/make-backlog-agent-ready","title":{"rendered":"How to Make Your Backlog Agent-Ready"},"content":{"rendered":"<p>Product teams are putting AI assistants to work across the lifecycle\u2014from drafting acceptance criteria to summarizing customer feedback and proposing test cases. But there\u2019s a catch: if your backlog lacks structure, agents fall back on generic, boilerplate output. The solution isn\u2019t clever prompts; it\u2019s a disciplined backlog that captures the who, what, why, and how so agents can respond with precision. In this guide, you\u2019ll find a practical checklist and copy-ready examples for StoriesOnBoard to make your work easy for AI to find, understand, and use.<\/p>\n<p>StoriesOnBoard is designed for this kind of clarity. Its story mapping hierarchy, collaborative workshops, and built-in AI features help you capture context once and reuse it throughout discovery, planning, and delivery. When your map reflects the full journey, your AI partner can deliver real value: suggest informed variants, generate relevant acceptance criteria, and help slice releases without losing the narrative thread.<\/p>\n<h2>The anatomy of an agent-ready backlog<\/h2>\n<ul>\n<li><strong>Clear title:<\/strong> Keep it concise and action-oriented, highlighting the user need or outcome. Example: \u201cEnable passwordless login via email magic link.\u201d<\/li>\n<li><strong>Concise description:<\/strong> A short paragraph on what changes for the user and why it matters. Skip technical deep-dives; stay user-centric.<\/li>\n<li><strong>User persona or role:<\/strong> Specify who benefits. Example: \u201cReturning shopper,\u201d \u201cWorkspace admin,\u201d or \u201cNew trial user.\u201d<\/li>\n<li><strong>User goal:<\/strong> What the user wants to do in their own words. Example: \u201cI want to sign in quickly without remembering a password.\u201d<\/li>\n<li><strong>Acceptance criteria:<\/strong> Testable conditions that define done. Favor scenario-style bullets that capture behavior and edge cases.<\/li>\n<li><strong>Release or milestone:<\/strong> Target timeframe or slice (e.g., MVP, Beta, GA, or a named release lane in StoriesOnBoard) so agents can prioritize scope.<\/li>\n<li><strong>Priority:<\/strong> A simple rank or label (e.g., P1\u2013P3) to guide sequencing and trade-offs.<\/li>\n<li><strong>Business value:<\/strong> Why it matters for the business\u2014revenue, retention, activation, support cost reduction, compliance.<\/li>\n<li><strong>Dependencies:<\/strong> Upstream or downstream work that must exist first (e.g., \u201cEmail service provider integration complete\u201d).<\/li>\n<li><strong>Assumptions:<\/strong> What you think is true but haven\u2019t validated (e.g., \u201cMost returning users have stable email access\u201d).<\/li>\n<li><strong>Constraints:<\/strong> Policy, legal, performance, or platform limits (e.g., \u201cMust be SOC 2 compliant; no PII in logs\u201d).<\/li>\n<li><strong>Edge cases:<\/strong> Rare but important scenarios (e.g., expired links, throttling, multiple device sign-ins).<\/li>\n<li><strong>Context rules:<\/strong> Style, tone, definition-of-done, data handling, or localization standards that apply across stories.<\/li>\n<\/ul>\n<h2>Why structure matters for AI agents<\/h2>\n<p>Large language models are great at pattern matching. If your backlog is vague, the pattern they match will be vague too. A story that says \u201cImprove login\u201d carries almost no signal about the user, business impact, or constraints\u2014so the agent defaults to generic best practices and boilerplate tests. The outputs aren\u2019t necessarily wrong; they\u2019re just not yours.<\/p>\n<p>Give an item a persona, goal, acceptance criteria, and context rules, and the agent knows what matters and which trade-offs are acceptable. Suddenly, the model can tailor its output: propose copy in your tone, flag privacy concerns that clash with SOC 2, or adjust acceptance tests for email throttling. Structure narrows the search space and raises relevance. In short, an agent-ready backlog helps AI produce drafts you can actually ship.<\/p>\n<h3>Agent-ready backlog checklist<\/h3>\n<ol>\n<li>Write titles with outcomes: lead with user value, not the UI element.<\/li>\n<li>Keep descriptions tight: one or two sentences that explain the change and benefit.<\/li>\n<li>Assign a persona or role: align to your StoriesOnBoard user types.<\/li>\n<li>State the user goal: capture the intent behind the task, not just the task.<\/li>\n<li>Draft acceptance criteria: use scenario-style bullets that reflect constraints and edge cases.<\/li>\n<li>Place the item in a release lane: MVP, Beta, or GA using StoriesOnBoard release groupings.<\/li>\n<li>Set priority: label with P1\u2013P3 or rank within the map for clear sequencing.<\/li>\n<li>Quantify business value: link to a metric like activation rate or ticket deflection.<\/li>\n<li>List dependencies: reference related cards or synced GitHub issues directly.<\/li>\n<li>Capture assumptions: make them explicit for discovery and useful agent prompts.<\/li>\n<li>Note constraints: compliance, performance budgets, platforms, or brand rules.<\/li>\n<li>Document edge cases: expired links, network drops, quota limits, time zones.<\/li>\n<li>Add context rules: tone of voice, definition of done, data handling standards.<\/li>\n<li>Sync with delivery: push refined stories to GitHub via StoriesOnBoard to keep a single source of truth.<\/li>\n<li>Review collaboratively: use live presence and comments to refine before sprint planning.<\/li>\n<\/ol>\n<h2>From vague to valuable: transforming tasks into an agent-ready backlog<\/h2>\n<p>Consider two takes on the same idea. The first says, \u201cImprove login.\u201d An AI agent might suggest \u201cMake it faster,\u201d \u201cAdd SSO,\u201d or \u201cImprove error messages.\u201d Some may help, but they ignore your users, your constraints, and your timeline.<\/p>\n<p>Now compare a well-formed story: \u201cAs a returning shopper, I want to sign in with a one-time email link so I don\u2019t have to remember a password. MVP will support English-only emails, rate-limited to prevent abuse.\u201d Acceptance criteria define behavior for expiration, throttling, and analytics. Dependencies reference the email provider setup. The agent can now draft on-brand email copy, a device test matrix, and a release note for returning shoppers. Same model, different input signal. Structure drives specificity.<\/p>\n<h2>Model-ready story maps in StoriesOnBoard<\/h2>\n<ul>\n<li><strong>Map the journey:<\/strong> Organize goals (activities), steps, and stories so agents see context\u2014where a story sits, what precedes it, and what success looks like.<\/li>\n<li><strong>Slice realistic MVPs:<\/strong> Use release lanes for MVP, Beta, and GA. Agents can tailor outputs to each slice, reducing scope creep.<\/li>\n<li><strong>Capture discovery fast:<\/strong> During workshops, add ideas as cards and turn them into structured stories using the visual text editor and AI helpers.<\/li>\n<li><strong>Maintain shared understanding:<\/strong> Keep personas, rules, and constraints on the map. Agents reference them when generating stories or criteria.<\/li>\n<li><strong>Connect planning to delivery:<\/strong> Sync stories with GitHub issues, filter by labels, and keep the story map as your source of truth.<\/li>\n<li><strong>Refine together:<\/strong> Live presence and comments help teams converge on wording before handoff.<\/li>\n<li><strong>Built-in AI assistance:<\/strong> Generate acceptance criteria, story drafts, and product text that inherit your map\u2019s context and tone.<\/li>\n<\/ul>\n<h3>Keeping an agent-ready backlog in StoriesOnBoard<\/h3>\n<p>Once the structure is set, consistency keeps it useful. Treat your story map as a living contract between product, design, engineering, and your AI helpers. When you refine stories, update assumptions and constraints\u2014not just titles. If a regulatory rule changes, adjust context rules once at the relevant activity or epic and let agents apply it everywhere. Use labels and release lanes as clear signals so both your AI and team know what\u2019s in scope for the next iteration. Because StoriesOnBoard sits above delivery tools, you can change strategy without losing track of what\u2019s in flight, and agents won\u2019t be stuck with stale tickets.<\/p>\n<section class=\"sob-related-section\">\n<h2>Spot journey gaps before they become rework<\/h2>\n<p>Even with solid structure, you might miss steps, error paths, or unlabeled edge cases. A quick agent-led review of your story map can reveal blind spots and turn them into clear backlog candidates\u2014start with this walkthrough on finding actionable <a href=\"https:\/\/storiesonboard.com\/blog\/ai-user-journey-gap-analysis\">Gaps<\/a>.<\/p>\n<\/section>\n<h2>Field-by-field examples<\/h2>\n<ul>\n<li><strong>Title:<\/strong> \u201cEnable passwordless login via email magic link (MVP).\u201d<\/li>\n<li><strong>Description:<\/strong> \u201cReturning shoppers can sign in with a one-time email link to reduce friction and raise repeat purchase rate.\u201d<\/li>\n<li><strong>User persona or role:<\/strong> Returning shopper on mobile web.<\/li>\n<li><strong>User goal:<\/strong> \u201cSign in quickly without remembering a password.\u201d<\/li>\n<li><strong>Acceptance criteria:<\/strong>\n<ul>\n<li>When a valid email is submitted, a one-time link is sent within 5 seconds.<\/li>\n<li>Links expire after 10 minutes or after first use, whichever occurs first.<\/li>\n<li>Attempting reuse returns a friendly error and logs an analytics event.<\/li>\n<li>Rate limit: max 3 emails per hour per address; show non-technical error when exceeded.<\/li>\n<li>On success, redirect to the last visited page; otherwise, home.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Release or milestone:<\/strong> MVP in Release 1; multilingual and device handoff in Release 2.<\/li>\n<li><strong>Priority:<\/strong> P1 for Q3 activation goals.<\/li>\n<li><strong>Business value:<\/strong> Expected +3% repeat purchase conversion; -15% \u201creset password\u201d support tickets.<\/li>\n<li><strong>Dependencies:<\/strong> Email provider integration; analytics event schema update; abuse prevention service.<\/li>\n<li><strong>Assumptions:<\/strong> Returning shoppers check email on the same device; inbox providers won\u2019t quarantine one-time links.<\/li>\n<li><strong>Constraints:<\/strong> SOC 2 logging; no PII beyond email; performance budget: TTFB &lt; 500 ms on send endpoint.<\/li>\n<li><strong>Edge cases:<\/strong> Shared inboxes; time zone differences on expiration; deep-link handling on iOS vs Android.<\/li>\n<li><strong>Context rules:<\/strong> Copy tone: friendly, concise; legal footer required; analytics naming convention: <em>auth.*<\/em>.<\/li>\n<\/ul>\n<h3>Edge cases and context rules that agents actually use<\/h3>\n<p>Edge cases teach agents how your product behaves under stress\u2014leading to better tests, clearer copy, and fewer surprises. For instance, if your context rule says links expire in ten minutes, the agent can suggest a countdown message and UX microcopy explaining why a link might fail. If your rules enforce a performance budget, the agent won\u2019t propose server-side techniques that blow response times. The more explicit your rules, the easier it is for AI to prune irrelevant options and converge on solutions your team would choose.<\/p>\n<section class=\"sob-related-section\">\n<h2>Spot journey gaps before they become rework<\/h2>\n<p>Even with solid structure, you may miss steps, error paths, or unlabeled edge cases. A quick agent-led review of your story map can surface blind spots and turn them into clear backlog candidates\u2014start with this walkthrough on finding actionable <a href=\"https:\/\/storiesonboard.com\/blog\/ai-user-journey-gap-analysis\">Gaps<\/a>.<\/p>\n<\/section>\n<h2>Collaboration patterns for an agent-ready team<\/h2>\n<p>The best teams use AI to accelerate alignment, not replace it. Start in StoriesOnBoard with a discovery workshop: map the journey from first touch to value realization, then brainstorm story candidates at each step. Invite engineering and support to annotate assumptions and constraints. Turn on live presence and tighten the wording in the modern visual text editor until anyone can explain the story in one breath. Then ask the built-in AI assistant to generate acceptance criteria\u2014and review them against your context rules. Small edits now beat expensive rework later.<\/p>\n<p>During backlog refinement, promote only the stories that meet your agent-ready checklist. Place them in the correct release lanes so agents know whether to target MVP or GA capabilities. Finally, sync to GitHub when you\u2019re ready to execute. Keep the story map as the narrative source of truth; mirror release and priority with labels in GitHub. Developers see the why behind the what, and your AI helpers get current, consistent inputs.<\/p>\n<section class=\"sob-related-section\">\n<h2>Plan smarter MVP slices with your agents<\/h2>\n<p>When release debates stall, align on the smallest outcome that proves value and let agents suggest variants within guardrails. For a practical approach to slicing releases with story maps, see our guide to <a href=\"https:\/\/storiesonboard.com\/blog\/mvp-slicing-ai-story-maps\">MVP<\/a> planning.<\/p>\n<\/section>\n<h3>Metrics to monitor your agent-ready backlog health<\/h3>\n<ul>\n<li><strong>Coverage:<\/strong> Percent of stories that include persona, goal, and acceptance criteria.<\/li>\n<li><strong>Constraint completeness:<\/strong> Stories that list dependencies, assumptions, and constraints.<\/li>\n<li><strong>Edge case density:<\/strong> Average number of meaningful edge cases per story in high-risk areas.<\/li>\n<li><strong>Release clarity:<\/strong> Share of stories assigned to a release lane vs a generic backlog pool.<\/li>\n<li><strong>AI usefulness rate:<\/strong> Ratio of AI-generated outputs accepted with minor edits vs major rewrites.<\/li>\n<li><strong>Rework reduction:<\/strong> Change requests or reopened tickets per story before vs after adopting structure.<\/li>\n<li><strong>Lead time to ready:<\/strong> Time from idea capture to \u201cready\u201d status after applying the checklist.<\/li>\n<\/ul>\n<h2>Avoiding common pitfalls when working with AI assistants<\/h2>\n<p>Vagueness is what drives generic AI output. If stories omit the persona or goal, the agent invents one. If constraints are missing, the agent suggests polished but unshippable solutions. And if acceptance criteria are fuzzy, tests stay superficial and bugs slip through. Another trap is scattering context\u2014tone in a doc, constraints in Slack, dependencies in a spreadsheet. Neither the model nor your teammates can piece that together reliably.<\/p>\n<p>Centralize context in StoriesOnBoard. Keep rules at the activity or epic level so they apply to all child stories. Use templates so every new card includes persona, goal, acceptance criteria, and business value. When constraints change, update them once and re-run the agent to refresh downstream drafts. Finally, don\u2019t stuff keywords. An agent-ready backlog is about clarity, not SEO. Short sentences, precise terms, and real examples beat buzzwords every time.<\/p>\n<h2>Frequently asked implementation questions<\/h2>\n<ul>\n<li><strong>How many acceptance criteria should a story have?<\/strong><br \/> Enough to define done unambiguously\u2014typically 5\u201310 bullets for complex flows. If you exceed that, split the story and adjust release lanes.<\/li>\n<li><strong>Where should context rules live?<\/strong><br \/> Put global rules at the map or activity level in StoriesOnBoard, and link them from individual stories. Local rules that affect only one story can live in the description.<\/li>\n<li><strong>What if we\u2019re still in discovery?<\/strong><br \/> Capture assumptions and constraints early, even if acceptance criteria are rough. Label the card \u201cDraft\u201d and keep it outside the MVP lane until validated.<\/li>\n<li><strong>How do we handle dependencies?<\/strong><br \/> Link related cards and synced GitHub issues. Add a brief note on dependency type (e.g., \u201ctechnical prerequisite\u201d vs \u201ccontent readiness\u201d).<\/li>\n<li><strong>Can the agent write user stories for us?<\/strong><br \/> Yes\u2014use StoriesOnBoard\u2019s AI assistance to draft stories and criteria, then review for alignment with persona, goals, and constraints before assigning a release.<\/li>\n<li><strong>What about privacy and compliance?<\/strong><br \/> List compliance requirements as constraints and context rules. The agent will incorporate them into copy, criteria, and test suggestions.<\/li>\n<li><strong>How do we keep the plan in sync with engineering?<\/strong><br \/> Use StoriesOnBoard\u2019s two-way sync with GitHub. Filter by labels, track progress, and keep the story map as your narrative source of truth.<\/li>\n<\/ul>\n<h2>Summary: Make your agent-ready backlog<\/h2>\n<p>An agent-ready backlog isn\u2019t about writing more\u2014it\u2019s about encoding the minimum structured context AI needs to be useful. Titles that signal outcomes. Descriptions in user terms. Personas, goals, and acceptance criteria that constrain behavior. Releases, priorities, and business value that guide trade-offs. Dependencies, assumptions, constraints, edge cases, and context rules that turn best practices into your practices.<\/p>\n<p>StoriesOnBoard keeps that structure visible and durable. Story maps preserve the end-to-end journey, release lanes frame scope, and built-in AI speeds drafting without losing the big picture. Centralize context and follow the checklist, and vague inputs disappear\u2014along with generic AI output. The payoff: clearer plans, faster refinement, fewer rewrites, and a team that moves from strategy to execution with confidence.<\/p>\n<section class=\"sob-faq-section\">\n<h2>Agent-Ready Backlog FAQ for Product Leaders<\/h2>\n<div class=\"sob-faq-section__items\">\n<article class=\"sob-faq-section__item\">\n<h3>What qualifies a backlog as agent-ready?<\/h3>\n<p>Structured context beats long prose. Include clear titles, persona and goal, acceptance criteria, release lane, priority, business value, dependencies, assumptions, constraints, edge cases, and context rules so AI outputs are tailored to your product.<\/p>\n<\/article>\n<article class=\"sob-faq-section__item\">\n<h3>How do we start if our backlog is scattered?<\/h3>\n<p>Centralize stories in StoriesOnBoard and apply the checklist to top-priority items first. Add map- or activity-level context rules and use templates to enforce persona, goals, and criteria on new cards.<\/p>\n<\/article>\n<article class=\"sob-faq-section__item\">\n<h3>How does this improve speed and quality?<\/h3>\n<p>It raises the AI usefulness rate and shortens lead time to ready by removing ambiguity. Clear acceptance criteria and constraints cut rework and help teams align faster.<\/p>\n<\/article>\n<article class=\"sob-faq-section__item\">\n<h3>When should we split a story?<\/h3>\n<p>If criteria exceed 5\u201310 bullets or multiple personas\/goals are mixed, split the work. Place slices in MVP, Beta, or GA lanes to protect scope and value.<\/p>\n<\/article>\n<article class=\"sob-faq-section__item\">\n<h3>How do we handle compliance and privacy?<\/h3>\n<p>Capture them as constraints and context rules (e.g., SOC 2, no PII in logs) at the map or activity level. Agents then inherit these guardrails for copy, tests, and acceptance criteria.<\/p>\n<\/article>\n<article class=\"sob-faq-section__item\">\n<h3>Can this coexist with GitHub workflows?<\/h3>\n<p>Yes. Keep the story map as the narrative source of truth and use StoriesOnBoard\u2019s two-way sync with GitHub, plus labels for release and priority, to keep engineering aligned.<\/p>\n<\/article>\n<article class=\"sob-faq-section__item\">\n<h3>Which metrics show it\u2019s working?<\/h3>\n<p>Track coverage, constraint completeness, edge case density, release clarity, AI usefulness rate, rework reduction, and lead time to ready. Upward trends confirm your structure is paying off.<\/p>\n<\/article>\n<article class=\"sob-faq-section__item\">\n<h3>How often should we revisit assumptions and rules?<\/h3>\n<p>Refresh them during discovery and regular refinement\u2014and whenever policies change. Centralized updates cascade to child stories so agents stay current.<\/p>\n<\/article>\n<article><\/article>\n<\/p><\/div>\n<\/section>\n<p><script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What qualifies a backlog as agent-ready?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Structured context beats long prose. Include clear titles, persona and goal, acceptance criteria, release lane, priority, business value, dependencies, assumptions, constraints, edge cases, and context rules so AI outputs are tailored to your product.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How do we start if our backlog is scattered?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Centralize stories in StoriesOnBoard and apply the checklist to top-priority items first. Add map- or activity-level context rules and use templates to enforce persona, goals, and criteria on new cards.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How does this improve speed and quality?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"It raises the AI usefulness rate and shortens lead time to ready by removing ambiguity. Clear acceptance criteria and constraints cut rework and help teams align faster.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"When should we split a story?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"If criteria exceed 5\u201310 bullets or multiple personas\/goals are mixed, split the work. Place slices in MVP, Beta, or GA lanes to protect scope and value.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How do we handle compliance and privacy?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Capture them as constraints and context rules (e.g., SOC 2, no PII in logs) at the map or activity level. Agents then inherit these guardrails for copy, tests, and acceptance criteria.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Can this coexist with GitHub workflows?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Yes. Keep the story map as the narrative source of truth and use StoriesOnBoard\u2019s two-way sync with GitHub, plus labels for release and priority, to keep engineering aligned.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Which metrics show it\u2019s working?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Track coverage, constraint completeness, edge case density, release clarity, AI usefulness rate, rework reduction, and lead time to ready. Upward trends confirm your structure is paying off.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How often should we revisit assumptions and rules?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Refresh them during discovery and regular refinement\u2014and whenever policies change. Centralized updates cascade to child stories so agents stay current.\"\n      }\n    }\n  ]\n}\n<\/script><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Agent-ready backlog: a practical checklist to structure user stories for AI agents in StoriesOnBoard, avoiding generic output and speeding delivery.<\/p>\n","protected":false},"author":13,"featured_media":6359,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-6360","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-story-mapping","resize-featured-image"],"_links":{"self":[{"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/posts\/6360","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/comments?post=6360"}],"version-history":[{"count":0,"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/posts\/6360\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/media\/6359"}],"wp:attachment":[{"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/media?parent=6360"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/categories?post=6360"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/storiesonboard.com\/blog\/wp-json\/wp\/v2\/tags?post=6360"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}