[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NHAS47STTJDF83MZ4401J":3,"skill-same:01M71NHAS47STTJDF83MZ4401J":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M71NHAS47STTJDF83MZ4401J","gds-sprint-status",null,"Summarize sprint status and surface risks. Use when the user says \"check sprint status\" or \"show sprint status\"","developAgent\u002Fbmad-start","developAgent","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F264530239?v=4","01M71J8X6CY24V5ZZHFGETRMSW","01M71J8X739FS28DGQAAY7V4QR",1,"MIT","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.iflow\u002Fskills\u002Fgds-sprint-status\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27],"sprint","sprint status","gds sprint status","status","show","use","when","check","user","summarize","2026-11-10 10:56:23",false,"---\nname: gds-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\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## Context\n\n- `project_context` = `**\u002Fproject-context.md` (load if exists)\n\n---\n\n## Conventions\n\n- Bare paths (e.g. `template.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\u002Fgds\u002Fconfig.yaml` and resolve:\n\n- `user_name`\n- `communication_language`\n- `implementation_artifacts`\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## 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:gds: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:gds: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:gds: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 (next_agent = DEVELOPER)\n  2. Else if any story status == review → recommend `code-review` for the first review story (next_agent = REVIEWER)\n  3. Else if any story status == ready-for-dev → recommend `dev-story` (next_agent = DEVELOPER)\n  4. Else if any story status == backlog → recommend `create-story` (next_agent = STORY_AUTHOR)\n  5. Else if any retrospective status == optional → recommend `retrospective` (next_agent = FACILITATOR)\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. Note: in the consolidated GDS Phase 4 model, all role labels (DEVELOPER, REVIEWER, STORY_AUTHOR, FACILITATOR) map to the same agent (gds-agent-game-dev \u002F Link Freeman). The labels are kept for downstream consumers that distinguish them semantically.\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:gds: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:gds: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>Exit workflow\u003C\u002Faction>\n  \u003C\u002Fcheck>\n\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!-- ========================= -->\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>next_agent = {{next_agent}}\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\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!-- ========================= -->\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\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## Context\n\n- `project_context` = `**\u002Fproject-context.md` (load if exists)\n\n---\n\n## Conventions\n\n- Bare paths (e.g. `template.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\u002Fgds\u002Fconfig.yaml` and resolve:\n\n- `user_name`\n- `communication_language`\n- `implementation_artifacts`\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## 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:gds: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:gds: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:gds: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 (next_agent = DEVELOPER)\n  2. Else if any story status == review → recommend `code-review` for the first review story (next_agent = REVIEWER)\n  3. Else if any story status == ready-for-dev → recommend `dev-story` (next_agent = DEVELOPER)\n  4. Else if any story status == backlog → recommend `create-story` (next_agent = STORY_AUTHOR)\n  5. Else if any retrospective status == optional → recommend `retrospective` (next_agent = FACILITATOR)\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. Note: in the consolidated GDS Phase 4 model, all role labels (DEVELOPER, REVIEWER, STORY_AUTHOR, FACILITATOR) map to the same agent (gds-agent-game-dev \u002F Link Freeman). The labels are kept for downstream consumers that distinguish them semantically.\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:gds: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:gds: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>Exit workflow\u003C\u002Faction>\n  \u003C\u002Fcheck>\n\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!-- ========================= -->\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>next_agent = {{next_agent}}\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\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!-- ========================= -->\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},"main","1907bbe850fb749efa8b499b8da7ebb78a663519",".iflow\u002Fskills\u002Fgds-sprint-status",0,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start","https:\u002F\u002Fgithub.com\u002FdevelopAgent","2026-07-19 05:19:22",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add developAgent\u002Fbmad-start --skill gds-sprint-status",{"tool":46,"command":47},"bunx","bunx skills add developAgent\u002Fbmad-start --skill gds-sprint-status",{"tool":49,"command":50},"pnpm","pnpm dlx skills add developAgent\u002Fbmad-start --skill gds-sprint-status","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.iflow\u002Fskills\u002Fgds-sprint-status\u002FSKILL.md",true,[54],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"customize.toml","OTHER","其他",1646,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.iflow\u002Fskills\u002Fgds-sprint-status\u002Fcustomize.toml",[61,81,113,130,144,170],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":72,"publishedAt":80},"01M71R3M9DJTTY0ARFQ6K04NMP","gds-correct-course","Manage significant changes during sprint execution. Use when the user says \"correct course\" or \"propose sprint change\"","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-correct-course\u002FSKILL.md",[67],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[73,74,75,26,76,77,24,23,78,79,18],"gds correct course","course","correct","changes","change","execution","manage","2026-11-10 13:02:02",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":95,"publishedAt":80},"01M71R3GENSFD1A1XVZTTQG1KF","gds-code-review","Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says \"run code review\" or \"review this code\"","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-code-review\u002FSKILL.md",[87,92],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":93,"categoryName":94,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000030","开发工程师",[96,97,98,99,100,76,101,102,103,104,105,106,107,24,108,23,109,110,111,112],"code review","code","review","gds code review","categories","triage","review code","run","parallel","case","with","run code","acceptance","edge","actionable","layers","hunter",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":80},"01M71R3DD098MQRD6F8S4GG0AW","gds-check-implementation-readiness","Verify GDD, UX, Architecture, and Epics alignment before production. Use when the user says \"check readiness\" or \"implementation readiness\"","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-check-implementation-readiness\u002FSKILL.md",[],[25,120,121,122,123,124,26,125,126,127,128,24,23,129],"readiness","Implementation Readiness","gds check implementation readiness","implementation","check readiness","Production","ux","verify","architecture","alignment",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":80},"01M71R3ACAA1G0NVQ330JQNJPK","gds-brainstorm-game","Facilitate game brainstorming sessions with game-specific techniques. Use when the user says \"brainstorm game\" or \"game ideas\"","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-brainstorm-game\u002FSKILL.md",[],[137,138,139,26,140,106,24,23,141,142,143],"gds brainstorm game","game","brainstorm","brainstorming","techniques","sessions","ideas",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":153,"publishedAt":80},"01M71R377MJ6WJTTFARGKH3HX7","gds-agent-tech-writer","Technical documentation specialist and knowledge curator for game projects. Use when the user asks to talk to Paige or requests the Technical Writer.","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-agent-tech-writer\u002FSKILL.md",[150],{"categoryNo":151,"categoryName":152,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000023","Skill与智能体开发",[154,155,156,157,23,158,159,160,161,24,26,162,163,164,165,166,167,168,138,169],"gds agent tech writer","tech","writer","technical writer","technical","knowledge","for","projects","technical documentation","talk","specialist","documentation specialist","knowledge curator","requests","documentation","curator",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":177,"publishedAt":80},"01M71R34RGT2ZX3TSFA2CRT0NC","gds-agent-game-solo-dev","Elite indie game developer for rapid prototyping and solo quick-flow development. Use when the user asks to talk to Indie or requests the Game Solo Dev.","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-agent-game-solo-dev\u002FSKILL.md",[176],{"categoryNo":151,"categoryName":152,"taxonomyType":90,"taxonomyTypeDesc":91},[178,138,179,180,181,182,26,163,167,183,184,24,23,185,160,186,187],"solo","gds agent game solo dev","dev","flow","developer","RAPID","game developer","prototyping","development","quick"]