[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FPD75WNB4KTPFN059CEJ33":3,"skill-same:01M6FPD75WNB4KTPFN059CEJ33":76},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6FPD75WNB4KTPFN059CEJ33","bmad-sprint-planning",null,"Generate sprint status tracking from epics. Use when the user says \"run sprint planning\" or \"generate sprint plan\"","reformlab\u002FReformLab","reformlab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F264161760?v=4","01M6CVRNMTPJRX8QX0P5J8NRZ6","01M6CVRNS5KTS18YC3AZHP1BZ3",1,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fbmad-sprint-planning\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30],"planning","bmad sprint planning","bmad","sprint planning","sprint","status","generate","run","plan","tracking","user","sprint plan","use","2026-11-10 10:12:30",false,"---\nname: bmad-sprint-planning\ndescription: 'Generate sprint status tracking from epics. Use when the user says \"run sprint planning\" or \"generate sprint plan\"'\n---\n\n# Sprint Planning Workflow\n\n**Goal:** Generate sprint status tracking from epics, detecting current story statuses and building a complete sprint-status.yaml file.\n\n**Your Role:** You are a Developer generating and maintaining sprint tracking. Parse epic files, detect story statuses, and produce a structured sprint-status.yaml.\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- `planning_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- Generate all documents in `{document_output_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- `tracking_system` = `file-system`\n- `project_key` = `NOKEY`\n- `story_location` = `{implementation_artifacts}`\n- `story_location_absolute` = `{implementation_artifacts}`\n- `epics_location` = `{planning_artifacts}`\n- `epics_pattern` = `*epic*.md`\n- `status_file` = `{implementation_artifacts}\u002Fsprint-status.yaml`\n\n## Input Files\n\n| Input | Path | Load Strategy |\n|-------|------|---------------|\n| Epics | `{planning_artifacts}\u002F*epic*.md` (whole) or `{planning_artifacts}\u002F*epic*\u002F*.md` (sharded) | FULL_LOAD |\n\n## Execution\n\n### Document Discovery - Full Epic Loading\n\n**Strategy**: Sprint planning needs ALL epics and stories to build complete status tracking.\n\n**Epic Discovery Process:**\n\n1. **Search for whole document first** - Look for `epics.md`, `bmm-epics.md`, or any `*epic*.md` file\n2. **Check for sharded version** - If whole document not found, look for `epics\u002Findex.md`\n3. **If sharded version found**:\n   - Read `index.md` to understand the document structure\n   - Read ALL epic section files listed in the index (e.g., `epic-1.md`, `epic-2.md`, etc.)\n   - Process all epics and their stories from the combined content\n   - This ensures complete sprint status coverage\n4. **Priority**: If both whole and sharded versions exist, use the whole document\n\n**Fuzzy matching**: Be flexible with document names - users may use variations like `epics.md`, `bmm-epics.md`, `user-stories.md`, etc.\n\n\u003Cworkflow>\n\n\u003Cstep n=\"1\" goal=\"Parse epic files and extract all work items\">\n\u003Caction>Load {project_context} for project-wide patterns and conventions (if exists)\u003C\u002Faction>\n\u003Caction>Communicate in {communication_language} with {user_name}\u003C\u002Faction>\n\u003Caction>Look for all files matching `{epics_pattern}` in {epics_location}\u003C\u002Faction>\n\u003Caction>Could be a single `epics.md` file or multiple `epic-1.md`, `epic-2.md` files\u003C\u002Faction>\n\n\u003Caction>For each epic file found, extract:\u003C\u002Faction>\n\n- Epic numbers from headers like `## Epic 1:` or `## Epic 2:`\n- Story IDs and titles from patterns like `### Story 1.1: User Authentication`\n- Convert story format from `Epic.Story: Title` to kebab-case key: `epic-story-title`\n\n**Story ID Conversion Rules:**\n\n- Original: `### Story 1.1: User Authentication`\n- Replace period with dash: `1-1`\n- Convert title to kebab-case: `user-authentication`\n- Final key: `1-1-user-authentication`\n\n\u003Caction>Build complete inventory of all epics and stories from all epic files\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"2\" goal=\"Build sprint status structure\">\n\u003Caction>For each epic found, create entries in this order:\u003C\u002Faction>\n\n1. **Epic entry** - Key: `epic-{num}`, Default status: `backlog`\n2. **Story entries** - Key: `{epic}-{story}-{title}`, Default status: `backlog`\n3. **Retrospective entry** - Key: `epic-{num}-retrospective`, Default status: `optional`\n\n**Example structure:**\n\n```yaml\ndevelopment_status:\n  epic-1: backlog\n  1-1-user-authentication: backlog\n  1-2-account-management: backlog\n  epic-1-retrospective: optional\n```\n\n\u003C\u002Fstep>\n\n\u003Cstep n=\"3\" goal=\"Apply intelligent status detection\">\n\u003Caction>For each story, detect current status by checking files:\u003C\u002Faction>\n\n**Story file detection:**\n\n- Check: `{story_location_absolute}\u002F{story-key}.md` (e.g., `stories\u002F1-1-user-authentication.md`)\n- If exists → upgrade status to at least `ready-for-dev`\n\n**Preservation rule:**\n\n- If existing `{status_file}` exists and has more advanced status, preserve it\n- Never downgrade status (e.g., don't change `done` to `ready-for-dev`)\n\n**Status Flow Reference:**\n\n- Epic: `backlog` → `in-progress` → `done`\n- Story: `backlog` → `ready-for-dev` → `in-progress` → `review` → `done`\n- Retrospective: `optional` ↔ `done`\n  \u003C\u002Fstep>\n\n\u003Cstep n=\"4\" goal=\"Generate sprint status file\">\n\u003Caction>Create or update {status_file} with:\u003C\u002Faction>\n\n**File Structure:**\n\n```yaml\n# generated: {date}\n# last_updated: {date}\n# project: {project_name}\n# project_key: {project_key}\n# tracking_system: {tracking_system}\n# story_location: {story_location}\n\n# STATUS DEFINITIONS:\n# ==================\n# Epic Status:\n#   - backlog: Epic not yet started\n#   - in-progress: Epic actively being worked on\n#   - done: All stories in epic completed\n#\n# Epic Status Transitions:\n#   - backlog → in-progress: Automatically when first story is created (via create-story)\n#   - in-progress → done: Manually when all stories reach 'done' status\n#\n# Story Status:\n#   - backlog: Story only exists in epic file\n#   - ready-for-dev: Story file created in stories folder\n#   - in-progress: Developer actively working on implementation\n#   - review: Ready for code review (via Dev's code-review workflow)\n#   - done: Story completed\n#\n# Retrospective Status:\n#   - optional: Can be completed but not required\n#   - done: Retrospective has been completed\n#\n# WORKFLOW NOTES:\n# ===============\n# - Epic transitions to 'in-progress' automatically when first story is created\n# - Stories can be worked in parallel if team capacity allows\n# - Developer typically creates next story after previous one is 'done' to incorporate learnings\n# - Dev moves story to 'review', then runs code-review (fresh context, different LLM recommended)\n\ngenerated: { date }\nlast_updated: { date }\nproject: { project_name }\nproject_key: { project_key }\ntracking_system: { tracking_system }\nstory_location: { story_location }\n\ndevelopment_status:\n  # All epics, stories, and retrospectives in order\n```\n\n\u003Caction>Write the complete sprint status YAML to {status_file}\u003C\u002Faction>\n\u003Caction>CRITICAL: Metadata appears TWICE - once as comments (#) for documentation, once as YAML key:value fields for parsing\u003C\u002Faction>\n\u003Caction>Ensure all items are ordered: epic, its stories, its retrospective, next epic...\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"5\" goal=\"Validate and report\">\n\u003Caction>Perform validation checks:\u003C\u002Faction>\n\n- [ ] Every epic in epic files appears in {status_file}\n- [ ] Every story in epic files appears in {status_file}\n- [ ] Every epic has a corresponding retrospective entry\n- [ ] No items in {status_file} that don't exist in epic files\n- [ ] All status values are legal (match state machine definitions)\n- [ ] File is valid YAML syntax\n\n\u003Caction>Count totals:\u003C\u002Faction>\n\n- Total epics: {{epic_count}}\n- Total stories: {{story_count}}\n- Epics in-progress: {{in_progress_count}}\n- Stories done: {{done_count}}\n\n\u003Caction>Display completion summary to {user_name} in {communication_language}:\u003C\u002Faction>\n\n**Sprint Status Generated Successfully**\n\n- **File Location:** {status_file}\n- **Total Epics:** {{epic_count}}\n- **Total Stories:** {{story_count}}\n- **Epics In Progress:** {{in_progress_count}}\n- **Stories Completed:** {{done_count}}\n\n**Next Steps:**\n\n1. Review the generated {status_file}\n2. Use this file to track development progress\n3. Agents will update statuses as they work\n4. Re-run this workflow to refresh auto-detected statuses\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\u002Fworkflow>\n\n## Additional Documentation\n\n### Status State Machine\n\n**Epic Status Flow:**\n\n```\nbacklog → in-progress → done\n```\n\n- **backlog**: Epic not yet started\n- **in-progress**: Epic actively being worked on (stories being created\u002Fimplemented)\n- **done**: All stories in epic completed\n\n**Story Status Flow:**\n\n```\nbacklog → ready-for-dev → in-progress → review → done\n```\n\n- **backlog**: Story only exists in epic file\n- **ready-for-dev**: Story file created (e.g., `stories\u002F1-3-plant-naming.md`)\n- **in-progress**: Developer actively working\n- **review**: Ready for code review (via Dev's code-review workflow)\n- **done**: Completed\n\n**Retrospective Status:**\n\n```\noptional ↔ done\n```\n\n- **optional**: Ready to be conducted but not required\n- **done**: Finished\n\n### Guidelines\n\n1. **Epic Activation**: Mark epic as `in-progress` when starting work on its first story\n2. **Sequential Default**: Stories are typically worked in order, but parallel work is supported\n3. **Parallel Work Supported**: Multiple stories can be `in-progress` if team capacity allows\n4. **Review Before Done**: Stories should pass through `review` before `done`\n5. **Learning Transfer**: Developer typically creates next story after previous one is `done` to incorporate learnings\n","# Sprint Planning Workflow\n\n**Goal:** Generate sprint status tracking from epics, detecting current story statuses and building a complete sprint-status.yaml file.\n\n**Your Role:** You are a Developer generating and maintaining sprint tracking. Parse epic files, detect story statuses, and produce a structured sprint-status.yaml.\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- `planning_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- Generate all documents in `{document_output_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- `tracking_system` = `file-system`\n- `project_key` = `NOKEY`\n- `story_location` = `{implementation_artifacts}`\n- `story_location_absolute` = `{implementation_artifacts}`\n- `epics_location` = `{planning_artifacts}`\n- `epics_pattern` = `*epic*.md`\n- `status_file` = `{implementation_artifacts}\u002Fsprint-status.yaml`\n\n## Input Files\n\n| Input | Path | Load Strategy |\n|-------|------|---------------|\n| Epics | `{planning_artifacts}\u002F*epic*.md` (whole) or `{planning_artifacts}\u002F*epic*\u002F*.md` (sharded) | FULL_LOAD |\n\n## Execution\n\n### Document Discovery - Full Epic Loading\n\n**Strategy**: Sprint planning needs ALL epics and stories to build complete status tracking.\n\n**Epic Discovery Process:**\n\n1. **Search for whole document first** - Look for `epics.md`, `bmm-epics.md`, or any `*epic*.md` file\n2. **Check for sharded version** - If whole document not found, look for `epics\u002Findex.md`\n3. **If sharded version found**:\n   - Read `index.md` to understand the document structure\n   - Read ALL epic section files listed in the index (e.g., `epic-1.md`, `epic-2.md`, etc.)\n   - Process all epics and their stories from the combined content\n   - This ensures complete sprint status coverage\n4. **Priority**: If both whole and sharded versions exist, use the whole document\n\n**Fuzzy matching**: Be flexible with document names - users may use variations like `epics.md`, `bmm-epics.md`, `user-stories.md`, etc.\n\n\u003Cworkflow>\n\n\u003Cstep n=\"1\" goal=\"Parse epic files and extract all work items\">\n\u003Caction>Load {project_context} for project-wide patterns and conventions (if exists)\u003C\u002Faction>\n\u003Caction>Communicate in {communication_language} with {user_name}\u003C\u002Faction>\n\u003Caction>Look for all files matching `{epics_pattern}` in {epics_location}\u003C\u002Faction>\n\u003Caction>Could be a single `epics.md` file or multiple `epic-1.md`, `epic-2.md` files\u003C\u002Faction>\n\n\u003Caction>For each epic file found, extract:\u003C\u002Faction>\n\n- Epic numbers from headers like `## Epic 1:` or `## Epic 2:`\n- Story IDs and titles from patterns like `### Story 1.1: User Authentication`\n- Convert story format from `Epic.Story: Title` to kebab-case key: `epic-story-title`\n\n**Story ID Conversion Rules:**\n\n- Original: `### Story 1.1: User Authentication`\n- Replace period with dash: `1-1`\n- Convert title to kebab-case: `user-authentication`\n- Final key: `1-1-user-authentication`\n\n\u003Caction>Build complete inventory of all epics and stories from all epic files\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"2\" goal=\"Build sprint status structure\">\n\u003Caction>For each epic found, create entries in this order:\u003C\u002Faction>\n\n1. **Epic entry** - Key: `epic-{num}`, Default status: `backlog`\n2. **Story entries** - Key: `{epic}-{story}-{title}`, Default status: `backlog`\n3. **Retrospective entry** - Key: `epic-{num}-retrospective`, Default status: `optional`\n\n**Example structure:**\n\n```yaml\ndevelopment_status:\n  epic-1: backlog\n  1-1-user-authentication: backlog\n  1-2-account-management: backlog\n  epic-1-retrospective: optional\n```\n\n\u003C\u002Fstep>\n\n\u003Cstep n=\"3\" goal=\"Apply intelligent status detection\">\n\u003Caction>For each story, detect current status by checking files:\u003C\u002Faction>\n\n**Story file detection:**\n\n- Check: `{story_location_absolute}\u002F{story-key}.md` (e.g., `stories\u002F1-1-user-authentication.md`)\n- If exists → upgrade status to at least `ready-for-dev`\n\n**Preservation rule:**\n\n- If existing `{status_file}` exists and has more advanced status, preserve it\n- Never downgrade status (e.g., don't change `done` to `ready-for-dev`)\n\n**Status Flow Reference:**\n\n- Epic: `backlog` → `in-progress` → `done`\n- Story: `backlog` → `ready-for-dev` → `in-progress` → `review` → `done`\n- Retrospective: `optional` ↔ `done`\n  \u003C\u002Fstep>\n\n\u003Cstep n=\"4\" goal=\"Generate sprint status file\">\n\u003Caction>Create or update {status_file} with:\u003C\u002Faction>\n\n**File Structure:**\n\n```yaml\n# generated: {date}\n# last_updated: {date}\n# project: {project_name}\n# project_key: {project_key}\n# tracking_system: {tracking_system}\n# story_location: {story_location}\n\n# STATUS DEFINITIONS:\n# ==================\n# Epic Status:\n#   - backlog: Epic not yet started\n#   - in-progress: Epic actively being worked on\n#   - done: All stories in epic completed\n#\n# Epic Status Transitions:\n#   - backlog → in-progress: Automatically when first story is created (via create-story)\n#   - in-progress → done: Manually when all stories reach 'done' status\n#\n# Story Status:\n#   - backlog: Story only exists in epic file\n#   - ready-for-dev: Story file created in stories folder\n#   - in-progress: Developer actively working on implementation\n#   - review: Ready for code review (via Dev's code-review workflow)\n#   - done: Story completed\n#\n# Retrospective Status:\n#   - optional: Can be completed but not required\n#   - done: Retrospective has been completed\n#\n# WORKFLOW NOTES:\n# ===============\n# - Epic transitions to 'in-progress' automatically when first story is created\n# - Stories can be worked in parallel if team capacity allows\n# - Developer typically creates next story after previous one is 'done' to incorporate learnings\n# - Dev moves story to 'review', then runs code-review (fresh context, different LLM recommended)\n\ngenerated: { date }\nlast_updated: { date }\nproject: { project_name }\nproject_key: { project_key }\ntracking_system: { tracking_system }\nstory_location: { story_location }\n\ndevelopment_status:\n  # All epics, stories, and retrospectives in order\n```\n\n\u003Caction>Write the complete sprint status YAML to {status_file}\u003C\u002Faction>\n\u003Caction>CRITICAL: Metadata appears TWICE - once as comments (#) for documentation, once as YAML key:value fields for parsing\u003C\u002Faction>\n\u003Caction>Ensure all items are ordered: epic, its stories, its retrospective, next epic...\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"5\" goal=\"Validate and report\">\n\u003Caction>Perform validation checks:\u003C\u002Faction>\n\n- [ ] Every epic in epic files appears in {status_file}\n- [ ] Every story in epic files appears in {status_file}\n- [ ] Every epic has a corresponding retrospective entry\n- [ ] No items in {status_file} that don't exist in epic files\n- [ ] All status values are legal (match state machine definitions)\n- [ ] File is valid YAML syntax\n\n\u003Caction>Count totals:\u003C\u002Faction>\n\n- Total epics: {{epic_count}}\n- Total stories: {{story_count}}\n- Epics in-progress: {{in_progress_count}}\n- Stories done: {{done_count}}\n\n\u003Caction>Display completion summary to {user_name} in {communication_language}:\u003C\u002Faction>\n\n**Sprint Status Generated Successfully**\n\n- **File Location:** {status_file}\n- **Total Epics:** {{epic_count}}\n- **Total Stories:** {{story_count}}\n- **Epics In Progress:** {{in_progress_count}}\n- **Stories Completed:** {{done_count}}\n\n**Next Steps:**\n\n1. Review the generated {status_file}\n2. Use this file to track development progress\n3. Agents will update statuses as they work\n4. Re-run this workflow to refresh auto-detected statuses\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\u002Fworkflow>\n\n## Additional Documentation\n\n### Status State Machine\n\n**Epic Status Flow:**\n\n```\nbacklog → in-progress → done\n```\n\n- **backlog**: Epic not yet started\n- **in-progress**: Epic actively being worked on (stories being created\u002Fimplemented)\n- **done**: All stories in epic completed\n\n**Story Status Flow:**\n\n```\nbacklog → ready-for-dev → in-progress → review → done\n```\n\n- **backlog**: Story only exists in epic file\n- **ready-for-dev**: Story file created (e.g., `stories\u002F1-3-plant-naming.md`)\n- **in-progress**: Developer actively working\n- **review**: Ready for code review (via Dev's code-review workflow)\n- **done**: Completed\n\n**Retrospective Status:**\n\n```\noptional ↔ done\n```\n\n- **optional**: Ready to be conducted but not required\n- **done**: Finished\n\n### Guidelines\n\n1. **Epic Activation**: Mark epic as `in-progress` when starting work on its first story\n2. **Sequential Default**: Stories are typically worked in order, but parallel work is supported\n3. **Parallel Work Supported**: Multiple stories can be `in-progress` if team capacity allows\n4. **Review Before Done**: Stories should pass through `review` before `done`\n5. **Learning Transfer**: Developer typically creates next story after previous one is `done` to incorporate learnings\n",{"name":5,"description":7},"master","314a64e40d9abca764698290593908a736500b30",".agents\u002Fskills\u002Fbmad-sprint-planning",0,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab","https:\u002F\u002Fdocs.reform-lab.eu\u002F","https:\u002F\u002Fgithub.com\u002Freformlab","https:\u002F\u002Freform-lab.eu\u002F","See who your policy actually helps","2026-05-25 03:50:07",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add reformlab\u002FReformLab --skill bmad-sprint-planning",{"tool":52,"command":53},"bunx","bunx skills add reformlab\u002FReformLab --skill bmad-sprint-planning",{"tool":55,"command":56},"pnpm","pnpm dlx skills add reformlab\u002FReformLab --skill bmad-sprint-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fbmad-sprint-planning\u002FSKILL.md",true,[60,66,72],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"checklist.md","REFERENCE","参考文档",1298,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fbmad-sprint-planning\u002Fchecklist.md",{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"customize.toml","OTHER","其他",1606,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fbmad-sprint-planning\u002Fcustomize.toml",{"path":73,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":74,"sourceHtmlUrl":75},"sprint-status-template.yaml",1790,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fbmad-sprint-planning\u002Fsprint-status-template.yaml",[77,100,114,138,155,170],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":31},"01M6FQK4CGE9096SN2JRE7DA8H","bmad-assist-help","Explain how bmad-assist works in this project by inspecting the local bmad-assist config, sprint status, epics, state, runs, prompts, logs, and relevant source code. Use when the user asks how bmad-assist behaves, how it reads epics and stories, why a run resumed or failed, what files are authoritative, or to investigate bmad-assist execution in the current repo.","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F_bmad\u002Fcore\u002Fskills\u002Fbmad-assist-help\u002FSKILL.md",[],[84,20,85,86,25,87,88,89,90,91,92,93,94,95,96,30,97,98,99,22],"help","bmad assist help","config","investigate","code","state","logs","execution","relevant","how","why","explain","repo","files","local","project",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":31},"01M6FQK133CMP4ZT00TW6S7TB1","bmad-fix-ci","Diagnose and fix GitHub CI failures locally. Use when the user says 'fix ci' or 'fix ci failures'.","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F_bmad\u002Fbmm\u002Fskills\u002Fbmad-fix-ci\u002FSKILL.md",[],[107,20,108,109,110,28,30,111,112,113],"bmad fix ci","ci","fix ci","fix","diagnose","fix ci failures","github",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":125,"publishedAt":31},"01M6FQJW69SATT3C9741MT2KJH","bmad-workflow-builder","Builds, converts, and analyzes workflows and skills. Use when the user requests to \"build a workflow\", \"modify a workflow\", \"quality check workflow\", \"analyze skill\", or \"convert a skill\".","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-workflow-builder\u002FSKILL.md",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[126,127,20,128,129,130,131,132,133,134,28,30,135,136,137],"bmad workflow builder","workflow","builder","workflow builder","workflows","convert","analyze","quality","check","build","quality check","requests",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":149,"publishedAt":31},"01M6FQJQMT5GW37ANR711FCBJR","bmad-validate-prd","Validate a PRD against standards. Use when the user says \"validate this PRD\" or \"run PRD validation\"","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-validate-prd\u002FSKILL.md",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[20,150,151,152,28,25,153,30,154],"bmad validate prd","prd","validate","validation","standards",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":164,"publishedAt":31},"01M6FQJMCSRVGCG65DAKKGW0M1","bmad-ux-designer","ux-designer agent","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-ux-designer\u002FSKILL.md",[161],{"categoryNo":162,"categoryName":163,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000032","设计师",[20,165,166,167,168,169],"bmad ux designer","UX Designer","designer","bmad ux","ux",{"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":179,"publishedAt":31},"01M6FQJDFKBXTWMBJD29FAC8TA","bmad-testarch-trace","Generate traceability matrix and quality gate decision. Use when the user says \"lets create traceability matrix\" or \"I want to analyze test coverage\"","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-testarch-trace\u002FSKILL.md",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000008","测试与质量",[180,181,182,20,183,184,185,24,132,133,186,28,187,30,188,189,190],"trace","bmad testarch","bmad testarch trace","test","quality gate","create","decision","coverage","test coverage","gate","traceability"]