[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6RVZZFYFFNXYJSDKB3CM9SS":3,"skill-same:01M6RVZZFYFFNXYJSDKB3CM9SS":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M6RVZZFYFFNXYJSDKB3CM9SS","bmad-sprint-status",null,"Summarize sprint status and surface risks. Use when the user says \"check sprint status\" or \"show sprint status\"","huangjia2019\u002Fsdd-in-action","huangjia2019","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F48795276?v=4","01M6RVB2A5TS40SQTN843K74XF","Jia Huang (黄佳)","01M6RVB2DWAKV004CDR8A4QXCY",175,"MIT","https:\u002F\u002Fgithub.com\u002Fhuangjia2019\u002Fsdd-in-action\u002Fblob\u002Fmaster\u002Fweek3\u002Fcode\u002F.agents\u002Fskills\u002Fbmad-sprint-status\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"status","bmad sprint status","bmad","sprint","summarize","check","user","use","show","when","2026-11-10 10:12:30",false,"---\nname: bmad-sprint-status\ndescription: 'Summarize sprint status and surface risks. Use when the user says \"check sprint status\" or \"show sprint status\"'\n---\n\n# Sprint Status Workflow\n\n**Goal:** Summarize sprint status, surface risks, and recommend the next workflow action.\n\n**Your Role:** You are a Developer providing clear, actionable sprint visibility. No time estimates — focus on status, risks, and next steps.\n\n## Conventions\n\n- Bare paths (e.g. `checklist.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml` and resolve:\n\n- `project_name`, `user_name`\n- `communication_language`, `document_output_language`\n- `implementation_artifacts`\n- `date` as system-generated current datetime\n- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## Paths\n\n- `sprint_status_file` = `{implementation_artifacts}\u002Fsprint-status.yaml`\n\n## Input Files\n\n| Input | Path | Load Strategy |\n|-------|------|---------------|\n| Sprint status | `{sprint_status_file}` | FULL_LOAD |\n\n## Execution\n\n\u003Cworkflow>\n\n\u003Cstep n=\"0\" goal=\"Determine execution mode\">\n  \u003Caction>Set mode = {{mode}} if provided by caller; otherwise mode = \"interactive\"\u003C\u002Faction>\n\n  \u003Ccheck if=\"mode == data\">\n    \u003Caction>Jump to Step 20\u003C\u002Faction>\n  \u003C\u002Fcheck>\n\n  \u003Ccheck if=\"mode == validate\">\n    \u003Caction>Jump to Step 30\u003C\u002Faction>\n  \u003C\u002Fcheck>\n\n  \u003Ccheck if=\"mode == interactive\">\n    \u003Caction>Continue to Step 1\u003C\u002Faction>\n  \u003C\u002Fcheck>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"1\" goal=\"Locate sprint status file\">\n  \u003Caction>Load {project_context} for project-wide patterns and conventions (if exists)\u003C\u002Faction>\n  \u003Caction>Try {sprint_status_file}\u003C\u002Faction>\n  \u003Ccheck if=\"file not found\">\n    \u003Coutput>sprint-status.yaml not found.\nRun `\u002Fbmad:bmm:workflows:sprint-planning` to generate it, then rerun sprint-status.\u003C\u002Foutput>\n    \u003Caction>Exit workflow\u003C\u002Faction>\n  \u003C\u002Fcheck>\n  \u003Caction>Continue to Step 2\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"2\" goal=\"Read and parse sprint-status.yaml\">\n  \u003Caction>Read the FULL file: {sprint_status_file}\u003C\u002Faction>\n  \u003Caction>Parse fields: generated, last_updated, project, project_key, tracking_system, story_location\u003C\u002Faction>\n  \u003Caction>Parse development_status map. Classify keys:\u003C\u002Faction>\n- Epics: keys starting with \"epic-\" (and not ending with \"-retrospective\")\n- Retrospectives: keys ending with \"-retrospective\"\n- Stories: everything else (e.g., 1-2-login-form)\n  \u003Caction>Map legacy story status \"drafted\" → \"ready-for-dev\"\u003C\u002Faction>\n  \u003Caction>Count story statuses: backlog, ready-for-dev, in-progress, review, done\u003C\u002Faction>\n  \u003Caction>Map legacy epic status \"contexted\" → \"in-progress\"\u003C\u002Faction>\n  \u003Caction>Count epic statuses: backlog, in-progress, done\u003C\u002Faction>\n  \u003Caction>Count retrospective statuses: optional, done\u003C\u002Faction>\n\n\u003Caction>Validate all statuses against known values:\u003C\u002Faction>\n\n- Valid story statuses: backlog, ready-for-dev, in-progress, review, done, drafted (legacy)\n- Valid epic statuses: backlog, in-progress, done, contexted (legacy)\n- Valid retrospective statuses: optional, done\n\n  \u003Ccheck if=\"any status is unrecognized\">\n    \u003Coutput>\n**Unknown status detected:**\n{{#each invalid_entries}}\n\n- `{{key}}`: \"{{status}}\" (not recognized)\n  {{\u002Feach}}\n\n**Valid statuses:**\n\n- Stories: backlog, ready-for-dev, in-progress, review, done\n- Epics: backlog, in-progress, done\n- Retrospectives: optional, done\n  \u003C\u002Foutput>\n  \u003Cask>How should these be corrected?\n  {{#each invalid_entries}}\n  {{@index}}. {{key}}: \"{{status}}\" → [select valid status]\n  {{\u002Feach}}\n\nEnter corrections (e.g., \"1=in-progress, 2=backlog\") or \"skip\" to continue without fixing:\u003C\u002Fask>\n\u003Ccheck if=\"user provided corrections\">\n\u003Caction>Update sprint-status.yaml with corrected values\u003C\u002Faction>\n\u003Caction>Re-parse the file with corrected statuses\u003C\u002Faction>\n\u003C\u002Fcheck>\n\u003C\u002Fcheck>\n\n\u003Caction>Detect risks:\u003C\u002Faction>\n\n- IF any story has status \"review\": suggest `\u002Fbmad:bmm:workflows:code-review`\n- IF any story has status \"in-progress\" AND no stories have status \"ready-for-dev\": recommend staying focused on active story\n- IF all epics have status \"backlog\" AND no stories have status \"ready-for-dev\": prompt `\u002Fbmad:bmm:workflows:create-story`\n- IF `last_updated` timestamp is more than 7 days old (or `last_updated` is missing, fall back to `generated`): warn \"sprint-status.yaml may be stale\"\n- IF any story key doesn't match an epic pattern (e.g., story \"5-1-...\" but no \"epic-5\"): warn \"orphaned story detected\"\n- IF any epic has status in-progress but has no associated stories: warn \"in-progress epic has no stories\"\n  \u003C\u002Fstep>\n\n\u003Cstep n=\"3\" goal=\"Select next action recommendation\">\n  \u003Caction>Pick the next recommended workflow using priority:\u003C\u002Faction>\n  \u003Cnote>When selecting \"first\" story: sort by epic number, then story number (e.g., 1-1 before 1-2 before 2-1)\u003C\u002Fnote>\n  1. If any story status == in-progress → recommend `dev-story` for the first in-progress story\n  2. Else if any story status == review → recommend `code-review` for the first review story\n  3. Else if any story status == ready-for-dev → recommend `dev-story`\n  4. Else if any story status == backlog → recommend `create-story`\n  5. Else if any retrospective status == optional → recommend `retrospective`\n  6. Else → All implementation items done; congratulate the user - you both did amazing work together!\n  \u003Caction>Store selected recommendation as: next_story_id, next_workflow_id, next_agent (DEV)\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"4\" goal=\"Display summary\">\n  \u003Coutput>\n## Sprint Status\n\n- Project: {{project}} ({{project_key}})\n- Tracking: {{tracking_system}}\n- Status file: {sprint_status_file}\n\n**Stories:** backlog {{count_backlog}}, ready-for-dev {{count_ready}}, in-progress {{count_in_progress}}, review {{count_review}}, done {{count_done}}\n\n**Epics:** backlog {{epic_backlog}}, in-progress {{epic_in_progress}}, done {{epic_done}}\n\n**Next Recommendation:** \u002Fbmad:bmm:workflows:{{next_workflow_id}} ({{next_story_id}})\n\n{{#if risks}}\n**Risks:**\n{{#each risks}}\n\n- {{this}}\n  {{\u002Feach}}\n  {{\u002Fif}}\n\n  \u003C\u002Foutput>\n  \u003C\u002Fstep>\n\n\u003Cstep n=\"5\" goal=\"Offer actions\">\n  \u003Cask>Pick an option:\n1) Run recommended workflow now\n2) Show all stories grouped by status\n3) Show raw sprint-status.yaml\n4) Exit\nChoice:\u003C\u002Fask>\n\n  \u003Ccheck if=\"choice == 1\">\n    \u003Coutput>Run `\u002Fbmad:bmm:workflows:{{next_workflow_id}}`.\nIf the command targets a story, set `story_key={{next_story_id}}` when prompted.\u003C\u002Foutput>\n  \u003C\u002Fcheck>\n\n  \u003Ccheck if=\"choice == 2\">\n    \u003Coutput>\n### Stories by Status\n- In Progress: {{stories_in_progress}}\n- Review: {{stories_in_review}}\n- Ready for Dev: {{stories_ready_for_dev}}\n- Backlog: {{stories_backlog}}\n- Done: {{stories_done}}\n    \u003C\u002Foutput>\n  \u003C\u002Fcheck>\n\n  \u003Ccheck if=\"choice == 3\">\n    \u003Caction>Display the full contents of {sprint_status_file}\u003C\u002Faction>\n  \u003C\u002Fcheck>\n\n  \u003Ccheck if=\"choice == 4\">\n    \u003Caction>Run: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.\u003C\u002Faction>\n    \u003Caction>Exit workflow\u003C\u002Faction>\n  \u003C\u002Fcheck>\n\u003C\u002Fstep>\n\n\u003C!-- ========================= -->\n\u003C!-- Data mode for other flows -->\n\u003C!-- ========================= -->\n\n\u003Cstep n=\"20\" goal=\"Data mode output\">\n  \u003Caction>Load and parse {sprint_status_file} same as Step 2\u003C\u002Faction>\n  \u003Caction>Compute recommendation same as Step 3\u003C\u002Faction>\n  \u003Ctemplate-output>next_workflow_id = {{next_workflow_id}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>next_story_id = {{next_story_id}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>count_backlog = {{count_backlog}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>count_ready = {{count_ready}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>count_in_progress = {{count_in_progress}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>count_review = {{count_review}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>count_done = {{count_done}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>epic_backlog = {{epic_backlog}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>epic_in_progress = {{epic_in_progress}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>epic_done = {{epic_done}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>risks = {{risks}}\u003C\u002Ftemplate-output>\n  \u003Caction>Return to caller\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003C!-- ========================= -->\n\u003C!-- Validate mode -->\n\u003C!-- ========================= -->\n\n\u003Cstep n=\"30\" goal=\"Validate sprint-status file\">\n  \u003Caction>Check that {sprint_status_file} exists\u003C\u002Faction>\n  \u003Ccheck if=\"missing\">\n    \u003Ctemplate-output>is_valid = false\u003C\u002Ftemplate-output>\n    \u003Ctemplate-output>error = \"sprint-status.yaml missing\"\u003C\u002Ftemplate-output>\n    \u003Ctemplate-output>suggestion = \"Run sprint-planning to create it\"\u003C\u002Ftemplate-output>\n    \u003Caction>Return\u003C\u002Faction>\n  \u003C\u002Fcheck>\n\n\u003Caction>Read and parse {sprint_status_file}\u003C\u002Faction>\n\n\u003Caction>Validate required metadata fields exist: generated, project, project_key, tracking_system, story_location (last_updated is optional for backward compatibility)\u003C\u002Faction>\n\u003Ccheck if=\"any required field missing\">\n\u003Ctemplate-output>is_valid = false\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>error = \"Missing required field(s): {{missing_fields}}\"\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>suggestion = \"Re-run sprint-planning or add missing fields manually\"\u003C\u002Ftemplate-output>\n\u003Caction>Return\u003C\u002Faction>\n\u003C\u002Fcheck>\n\n\u003Caction>Verify development_status section exists with at least one entry\u003C\u002Faction>\n\u003Ccheck if=\"development_status missing or empty\">\n\u003Ctemplate-output>is_valid = false\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>error = \"development_status missing or empty\"\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>suggestion = \"Re-run sprint-planning or repair the file manually\"\u003C\u002Ftemplate-output>\n\u003Caction>Return\u003C\u002Faction>\n\u003C\u002Fcheck>\n\n\u003Caction>Validate all status values against known valid statuses:\u003C\u002Faction>\n\n- Stories: backlog, ready-for-dev, in-progress, review, done (legacy: drafted)\n- Epics: backlog, in-progress, done (legacy: contexted)\n- Retrospectives: optional, done\n  \u003Ccheck if=\"any invalid status found\">\n  \u003Ctemplate-output>is_valid = false\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>error = \"Invalid status values: {{invalid_entries}}\"\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>suggestion = \"Fix invalid statuses in sprint-status.yaml\"\u003C\u002Ftemplate-output>\n  \u003Caction>Return\u003C\u002Faction>\n  \u003C\u002Fcheck>\n\n\u003Ctemplate-output>is_valid = true\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>message = \"sprint-status.yaml valid: metadata complete, all statuses recognized\"\u003C\u002Ftemplate-output>\n\u003Caction>Run: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003C\u002Fworkflow>\n","# Sprint Status Workflow\n\n**Goal:** Summarize sprint status, surface risks, and recommend the next workflow action.\n\n**Your Role:** You are a Developer providing clear, actionable sprint visibility. No time estimates — focus on status, risks, and next steps.\n\n## Conventions\n\n- Bare paths (e.g. `checklist.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml` and resolve:\n\n- `project_name`, `user_name`\n- `communication_language`, `document_output_language`\n- `implementation_artifacts`\n- `date` as system-generated current datetime\n- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## Paths\n\n- `sprint_status_file` = `{implementation_artifacts}\u002Fsprint-status.yaml`\n\n## Input Files\n\n| Input | Path | Load Strategy |\n|-------|------|---------------|\n| Sprint status | `{sprint_status_file}` | FULL_LOAD |\n\n## Execution\n\n\u003Cworkflow>\n\n\u003Cstep n=\"0\" goal=\"Determine execution mode\">\n  \u003Caction>Set mode = {{mode}} if provided by caller; otherwise mode = \"interactive\"\u003C\u002Faction>\n\n  \u003Ccheck if=\"mode == data\">\n    \u003Caction>Jump to Step 20\u003C\u002Faction>\n  \u003C\u002Fcheck>\n\n  \u003Ccheck if=\"mode == validate\">\n    \u003Caction>Jump to Step 30\u003C\u002Faction>\n  \u003C\u002Fcheck>\n\n  \u003Ccheck if=\"mode == interactive\">\n    \u003Caction>Continue to Step 1\u003C\u002Faction>\n  \u003C\u002Fcheck>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"1\" goal=\"Locate sprint status file\">\n  \u003Caction>Load {project_context} for project-wide patterns and conventions (if exists)\u003C\u002Faction>\n  \u003Caction>Try {sprint_status_file}\u003C\u002Faction>\n  \u003Ccheck if=\"file not found\">\n    \u003Coutput>sprint-status.yaml not found.\nRun `\u002Fbmad:bmm:workflows:sprint-planning` to generate it, then rerun sprint-status.\u003C\u002Foutput>\n    \u003Caction>Exit workflow\u003C\u002Faction>\n  \u003C\u002Fcheck>\n  \u003Caction>Continue to Step 2\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"2\" goal=\"Read and parse sprint-status.yaml\">\n  \u003Caction>Read the FULL file: {sprint_status_file}\u003C\u002Faction>\n  \u003Caction>Parse fields: generated, last_updated, project, project_key, tracking_system, story_location\u003C\u002Faction>\n  \u003Caction>Parse development_status map. Classify keys:\u003C\u002Faction>\n- Epics: keys starting with \"epic-\" (and not ending with \"-retrospective\")\n- Retrospectives: keys ending with \"-retrospective\"\n- Stories: everything else (e.g., 1-2-login-form)\n  \u003Caction>Map legacy story status \"drafted\" → \"ready-for-dev\"\u003C\u002Faction>\n  \u003Caction>Count story statuses: backlog, ready-for-dev, in-progress, review, done\u003C\u002Faction>\n  \u003Caction>Map legacy epic status \"contexted\" → \"in-progress\"\u003C\u002Faction>\n  \u003Caction>Count epic statuses: backlog, in-progress, done\u003C\u002Faction>\n  \u003Caction>Count retrospective statuses: optional, done\u003C\u002Faction>\n\n\u003Caction>Validate all statuses against known values:\u003C\u002Faction>\n\n- Valid story statuses: backlog, ready-for-dev, in-progress, review, done, drafted (legacy)\n- Valid epic statuses: backlog, in-progress, done, contexted (legacy)\n- Valid retrospective statuses: optional, done\n\n  \u003Ccheck if=\"any status is unrecognized\">\n    \u003Coutput>\n**Unknown status detected:**\n{{#each invalid_entries}}\n\n- `{{key}}`: \"{{status}}\" (not recognized)\n  {{\u002Feach}}\n\n**Valid statuses:**\n\n- Stories: backlog, ready-for-dev, in-progress, review, done\n- Epics: backlog, in-progress, done\n- Retrospectives: optional, done\n  \u003C\u002Foutput>\n  \u003Cask>How should these be corrected?\n  {{#each invalid_entries}}\n  {{@index}}. {{key}}: \"{{status}}\" → [select valid status]\n  {{\u002Feach}}\n\nEnter corrections (e.g., \"1=in-progress, 2=backlog\") or \"skip\" to continue without fixing:\u003C\u002Fask>\n\u003Ccheck if=\"user provided corrections\">\n\u003Caction>Update sprint-status.yaml with corrected values\u003C\u002Faction>\n\u003Caction>Re-parse the file with corrected statuses\u003C\u002Faction>\n\u003C\u002Fcheck>\n\u003C\u002Fcheck>\n\n\u003Caction>Detect risks:\u003C\u002Faction>\n\n- IF any story has status \"review\": suggest `\u002Fbmad:bmm:workflows:code-review`\n- IF any story has status \"in-progress\" AND no stories have status \"ready-for-dev\": recommend staying focused on active story\n- IF all epics have status \"backlog\" AND no stories have status \"ready-for-dev\": prompt `\u002Fbmad:bmm:workflows:create-story`\n- IF `last_updated` timestamp is more than 7 days old (or `last_updated` is missing, fall back to `generated`): warn \"sprint-status.yaml may be stale\"\n- IF any story key doesn't match an epic pattern (e.g., story \"5-1-...\" but no \"epic-5\"): warn \"orphaned story detected\"\n- IF any epic has status in-progress but has no associated stories: warn \"in-progress epic has no stories\"\n  \u003C\u002Fstep>\n\n\u003Cstep n=\"3\" goal=\"Select next action recommendation\">\n  \u003Caction>Pick the next recommended workflow using priority:\u003C\u002Faction>\n  \u003Cnote>When selecting \"first\" story: sort by epic number, then story number (e.g., 1-1 before 1-2 before 2-1)\u003C\u002Fnote>\n  1. If any story status == in-progress → recommend `dev-story` for the first in-progress story\n  2. Else if any story status == review → recommend `code-review` for the first review story\n  3. Else if any story status == ready-for-dev → recommend `dev-story`\n  4. Else if any story status == backlog → recommend `create-story`\n  5. Else if any retrospective status == optional → recommend `retrospective`\n  6. Else → All implementation items done; congratulate the user - you both did amazing work together!\n  \u003Caction>Store selected recommendation as: next_story_id, next_workflow_id, next_agent (DEV)\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"4\" goal=\"Display summary\">\n  \u003Coutput>\n## Sprint Status\n\n- Project: {{project}} ({{project_key}})\n- Tracking: {{tracking_system}}\n- Status file: {sprint_status_file}\n\n**Stories:** backlog {{count_backlog}}, ready-for-dev {{count_ready}}, in-progress {{count_in_progress}}, review {{count_review}}, done {{count_done}}\n\n**Epics:** backlog {{epic_backlog}}, in-progress {{epic_in_progress}}, done {{epic_done}}\n\n**Next Recommendation:** \u002Fbmad:bmm:workflows:{{next_workflow_id}} ({{next_story_id}})\n\n{{#if risks}}\n**Risks:**\n{{#each risks}}\n\n- {{this}}\n  {{\u002Feach}}\n  {{\u002Fif}}\n\n  \u003C\u002Foutput>\n  \u003C\u002Fstep>\n\n\u003Cstep n=\"5\" goal=\"Offer actions\">\n  \u003Cask>Pick an option:\n1) Run recommended workflow now\n2) Show all stories grouped by status\n3) Show raw sprint-status.yaml\n4) Exit\nChoice:\u003C\u002Fask>\n\n  \u003Ccheck if=\"choice == 1\">\n    \u003Coutput>Run `\u002Fbmad:bmm:workflows:{{next_workflow_id}}`.\nIf the command targets a story, set `story_key={{next_story_id}}` when prompted.\u003C\u002Foutput>\n  \u003C\u002Fcheck>\n\n  \u003Ccheck if=\"choice == 2\">\n    \u003Coutput>\n### Stories by Status\n- In Progress: {{stories_in_progress}}\n- Review: {{stories_in_review}}\n- Ready for Dev: {{stories_ready_for_dev}}\n- Backlog: {{stories_backlog}}\n- Done: {{stories_done}}\n    \u003C\u002Foutput>\n  \u003C\u002Fcheck>\n\n  \u003Ccheck if=\"choice == 3\">\n    \u003Caction>Display the full contents of {sprint_status_file}\u003C\u002Faction>\n  \u003C\u002Fcheck>\n\n  \u003Ccheck if=\"choice == 4\">\n    \u003Caction>Run: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.\u003C\u002Faction>\n    \u003Caction>Exit workflow\u003C\u002Faction>\n  \u003C\u002Fcheck>\n\u003C\u002Fstep>\n\n\u003C!-- ========================= -->\n\u003C!-- Data mode for other flows -->\n\u003C!-- ========================= -->\n\n\u003Cstep n=\"20\" goal=\"Data mode output\">\n  \u003Caction>Load and parse {sprint_status_file} same as Step 2\u003C\u002Faction>\n  \u003Caction>Compute recommendation same as Step 3\u003C\u002Faction>\n  \u003Ctemplate-output>next_workflow_id = {{next_workflow_id}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>next_story_id = {{next_story_id}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>count_backlog = {{count_backlog}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>count_ready = {{count_ready}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>count_in_progress = {{count_in_progress}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>count_review = {{count_review}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>count_done = {{count_done}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>epic_backlog = {{epic_backlog}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>epic_in_progress = {{epic_in_progress}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>epic_done = {{epic_done}}\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>risks = {{risks}}\u003C\u002Ftemplate-output>\n  \u003Caction>Return to caller\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003C!-- ========================= -->\n\u003C!-- Validate mode -->\n\u003C!-- ========================= -->\n\n\u003Cstep n=\"30\" goal=\"Validate sprint-status file\">\n  \u003Caction>Check that {sprint_status_file} exists\u003C\u002Faction>\n  \u003Ccheck if=\"missing\">\n    \u003Ctemplate-output>is_valid = false\u003C\u002Ftemplate-output>\n    \u003Ctemplate-output>error = \"sprint-status.yaml missing\"\u003C\u002Ftemplate-output>\n    \u003Ctemplate-output>suggestion = \"Run sprint-planning to create it\"\u003C\u002Ftemplate-output>\n    \u003Caction>Return\u003C\u002Faction>\n  \u003C\u002Fcheck>\n\n\u003Caction>Read and parse {sprint_status_file}\u003C\u002Faction>\n\n\u003Caction>Validate required metadata fields exist: generated, project, project_key, tracking_system, story_location (last_updated is optional for backward compatibility)\u003C\u002Faction>\n\u003Ccheck if=\"any required field missing\">\n\u003Ctemplate-output>is_valid = false\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>error = \"Missing required field(s): {{missing_fields}}\"\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>suggestion = \"Re-run sprint-planning or add missing fields manually\"\u003C\u002Ftemplate-output>\n\u003Caction>Return\u003C\u002Faction>\n\u003C\u002Fcheck>\n\n\u003Caction>Verify development_status section exists with at least one entry\u003C\u002Faction>\n\u003Ccheck if=\"development_status missing or empty\">\n\u003Ctemplate-output>is_valid = false\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>error = \"development_status missing or empty\"\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>suggestion = \"Re-run sprint-planning or repair the file manually\"\u003C\u002Ftemplate-output>\n\u003Caction>Return\u003C\u002Faction>\n\u003C\u002Fcheck>\n\n\u003Caction>Validate all status values against known valid statuses:\u003C\u002Faction>\n\n- Stories: backlog, ready-for-dev, in-progress, review, done (legacy: drafted)\n- Epics: backlog, in-progress, done (legacy: contexted)\n- Retrospectives: optional, done\n  \u003Ccheck if=\"any invalid status found\">\n  \u003Ctemplate-output>is_valid = false\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>error = \"Invalid status values: {{invalid_entries}}\"\u003C\u002Ftemplate-output>\n  \u003Ctemplate-output>suggestion = \"Fix invalid statuses in sprint-status.yaml\"\u003C\u002Ftemplate-output>\n  \u003Caction>Return\u003C\u002Faction>\n  \u003C\u002Fcheck>\n\n\u003Ctemplate-output>is_valid = true\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>message = \"sprint-status.yaml valid: metadata complete, all statuses recognized\"\u003C\u002Ftemplate-output>\n\u003Caction>Run: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003C\u002Fworkflow>\n",{"name":5,"description":7},"master","7ccc24b38f7cae09897ace41ebae14780250ac86","week3\u002Fcode\u002F.agents\u002Fskills\u002Fbmad-sprint-status",60,"https:\u002F\u002Fgithub.com\u002Fhuangjia2019\u002Fsdd-in-action","https:\u002F\u002Fgithub.com\u002Fhuangjia2019","https:\u002F\u002Fkage-ai.com","AI researcher at A*STAR | Author of Designing AI Agents (Manning) | Co-founder of ADPS","2026-08-25 16:05:09",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add huangjia2019\u002Fsdd-in-action --skill bmad-sprint-status",{"tool":49,"command":50},"bunx","bunx skills add huangjia2019\u002Fsdd-in-action --skill bmad-sprint-status",{"tool":52,"command":53},"pnpm","pnpm dlx skills add huangjia2019\u002Fsdd-in-action --skill bmad-sprint-status","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhuangjia2019\u002Fsdd-in-action\u002Fblob\u002Fmaster\u002Fweek3\u002Fcode\u002F.agents\u002Fskills\u002Fbmad-sprint-status\u002FSKILL.md",true,[57],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"customize.toml","OTHER","其他",1609,"https:\u002F\u002Fgithub.com\u002Fhuangjia2019\u002Fsdd-in-action\u002Fblob\u002Fmaster\u002Fweek3\u002Fcode\u002F.agents\u002Fskills\u002Fbmad-sprint-status\u002Fcustomize.toml",[64,84,99,116,131,146],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":29},"01M6WZBHKBA02YT2SHSACNJR91","openspec-verify-change","Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.","https:\u002F\u002Fgithub.com\u002Fhuangjia2019\u002Fsdd-in-action\u002Fblob\u002Fmaster\u002Fweek3\u002Fcode\u002F.opencode\u002Fskills\u002Fopenspec-verify-change\u002FSKILL.md",[],[71,72,73,74,75,28,76,77,78,79,80,26,25,81,82,83],"change","openspec verify change","verify","verify change","openspec","validate","complete","verify implementation","coherent","implementation","correct","artifacts","cli",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":29},"01M6WZBEQRPC45MDYVPMG17X89","openspec-sync-specs","Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.","https:\u002F\u002Fgithub.com\u002Fhuangjia2019\u002Fsdd-in-action\u002Fblob\u002Fmaster\u002Fweek3\u002Fcode\u002F.opencode\u002Fskills\u002Fopenspec-sync-specs\u002FSKILL.md",[],[91,92,75,71,93,83,94,28,95,96,97,98,26,25],"openspec sync specs","sync","spec","update","changes","with","main","delta",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":29},"01M6WZBA2QKBW10Z1ZYA4K2AV9","openspec-propose","Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.","https:\u002F\u002Fgithub.com\u002Fhuangjia2019\u002Fsdd-in-action\u002Fblob\u002Fmaster\u002Fweek3\u002Fcode\u002F.opencode\u002Fskills\u002Fopenspec-propose\u002FSKILL.md",[],[106,75,28,80,107,77,108,109,110,96,111,112,113,25,82,114,71,83,115,26],"openspec propose","build","describe","for","ready","get","proposal","generated","tasks","design",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":29},"01M6WZB3J0FJQJ0WSW9EK6447P","openspec-onboard","Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.","https:\u002F\u002Fgithub.com\u002Fhuangjia2019\u002Fsdd-in-action\u002Fblob\u002Fmaster\u002Fweek3\u002Fcode\u002F.opencode\u002Fskills\u002Fopenspec-onboard\u002FSKILL.md",[],[123,124,75,96,125,109,77,126,127,128,129,130,83],"openspec onboard","onboard","codebase","cycle","narration","work","onboarding","workflow",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":29},"01M6WZAZX6QSAV79619M68K8N1","openspec-new-change","Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.","https:\u002F\u002Fgithub.com\u002Fhuangjia2019\u002Fsdd-in-action\u002Fblob\u002Fmaster\u002Fweek3\u002Fcode\u002F.opencode\u002Fskills\u002Fopenspec-new-change\u002FSKILL.md",[],[71,75,138,139,140,26,141,142,25,143,144,130,83,145,28,96],"openspec new change","structured","artifact","new feature","fix","start","create","feature",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":29},"01M6WZAX8300NEPY3T1J8FRS3C","openspec-ff-change","Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.","https:\u002F\u002Fgithub.com\u002Fhuangjia2019\u002Fsdd-in-action\u002Fblob\u002Fmaster\u002Fweek3\u002Fcode\u002F.opencode\u002Fskills\u002Fopenspec-ff-change\u002FSKILL.md",[],[71,153,75,83,28,109,154,140,80,26,25,155,82,144],"openspec ff change","creation","fast"]