[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DNJXQ7DXBS0NN4CBX0M01P":3,"skill-same:01M6DNJXQ7DXBS0NN4CBX0M01P":73},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M6DNJXQ7DXBS0NN4CBX0M01P","aac-sprint-planning",null,"Generate sprint status tracking from epics. Use when the user says \"run sprint planning\" or \"generate sprint plan\"","msayedshokry\u002FAgileAgentCanvasExt","msayedshokry","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F35009459?v=4","01M6DN5RZZ297CGWTNJ6ERZQ8W","Mohamed Sayed","01M6DN5S4XS7SVCSXZRW2XR0XF",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-sprint-planning\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"planning","sprint planning","sprint","aac sprint planning","status","generate","run","plan","tracking","user","sprint plan","use","2026-11-10 10:12:30",false,"---\nname: aac-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 EXACTLY this structure. Do NOT add, remove, or rename any top-level field.\u003C\u002Faction>\n\n**CRITICAL — Exact Field List (top level):**\n\nThe file MUST contain these fields and NO others at the top level:\n- `generated` — string, human-readable timestamp\n- `last_updated` — string, same format as generated\n- `project` — string, project name\n- `project_key` — string, always \"NOKEY\" for file-system tracking\n- `tracking_system` — string, always \"file-system\"\n- `story_location` — string, path to story files\n- `development_status` — object, flat map of all items\n- `sprints` — OPTIONAL object, only if you are grouping stories into sprints\n\n**Date format:** Use `YYYY-MM-DD HH:MM` (24-hour clock, no timezone). Example: `2026-06-05 14:30`.\n\n**Dual metadata rule:** The file header contains the SAME metadata twice:\n1. As YAML comments (`# key: value`) — for human readers\n2. As YAML key:value pairs — for machine parsing\nBoth must match exactly. Do NOT skip either form.\n\n**Complete file template:**\n\n```yaml\n# generated: 2026-06-05 14:30\n# last_updated: 2026-06-05 14:30\n# project: {project_name}\n# project_key: NOKEY\n# tracking_system: file-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# 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\ngenerated: 2026-06-05 14:30\nlast_updated: 2026-06-05 14:30\nproject: {project_name}\nproject_key: NOKEY\ntracking_system: file-system\nstory_location: {story_location}\n\ndevelopment_status:\n  epic-1: backlog\n  1-1-user-authentication: backlog\n  1-2-account-management: backlog\n  epic-1-retrospective: optional\n  epic-2: backlog\n  2-1-personality-system: backlog\n  epic-2-retrospective: optional\n```\n\n**Key format rules (EXACT — do not deviate):**\n\n| Item type | Pattern | Example |\n|-----------|---------|---------|\n| Epic | `epic-{N}` | `epic-1`, `epic-2` |\n| Story | `{N}-{M}-{kebab-title}` | `1-1-user-authentication`, `2-1-personality-system` |\n| Retrospective | `epic-{N}-retrospective` | `epic-1-retrospective` |\n\nStory key conversion from epic file:\n1. Take the story header: `### Story 1.1: User Authentication`\n2. Replace the period with a dash: `1-1`\n3. Convert the title to kebab-case (lowercase, spaces → hyphens, remove special chars): `user-authentication`\n4. Combine: `1-1-user-authentication`\n\n**Status rules (per item type — NEVER mix):**\n\n| Item type | Valid statuses | Default for new items |\n|-----------|---------------|----------------------|\n| Epic | `backlog`, `in-progress`, `done` | `backlog` |\n| Story | `backlog`, `ready-for-dev`, `in-progress`, `review`, `done` | `backlog` |\n| Retrospective | `optional`, `done` | `optional` |\n\n**Ordering rule:** Items MUST appear in this sequence: epic-N, all its stories in story-number order, epic-N-retrospective, then epic-(N+1), etc.\n\n**Sprints section (OPTIONAL):**\n\nOnly add `sprints:` if you are explicitly grouping stories into named sprints. If unsure, omit it entirely.\n\n```yaml\nsprints:\n  sprint_1:\n    goal: \"MVP core features\"\n    start_date: \"2026-06-01\"\n    end_date: \"2026-06-14\"\n    stories:\n      - epic-1\n      - 1-1-user-authentication\n      - 1-2-account-management\n      - epic-1-retrospective\n```\n\nEvery key in a sprint's `stories` list MUST exist in `development_status`.\n\n\u003Caction>Write the complete sprint status YAML to {status_file}\u003C\u002Faction>\n\u003Caction>CRITICAL: Do NOT add any top-level fields not listed above (no version, no notes, no summary, no health, no velocity)\u003C\u002Faction>\n\u003Caction>CRITICAL: Do NOT use camelCase field names — use exactly snake_case as shown\u003C\u002Faction>\n\u003Caction>CRITICAL: Do NOT use legacy status aliases \"drafted\" or \"contexted\" — use the canonical forms\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 EXACTLY this structure. Do NOT add, remove, or rename any top-level field.\u003C\u002Faction>\n\n**CRITICAL — Exact Field List (top level):**\n\nThe file MUST contain these fields and NO others at the top level:\n- `generated` — string, human-readable timestamp\n- `last_updated` — string, same format as generated\n- `project` — string, project name\n- `project_key` — string, always \"NOKEY\" for file-system tracking\n- `tracking_system` — string, always \"file-system\"\n- `story_location` — string, path to story files\n- `development_status` — object, flat map of all items\n- `sprints` — OPTIONAL object, only if you are grouping stories into sprints\n\n**Date format:** Use `YYYY-MM-DD HH:MM` (24-hour clock, no timezone). Example: `2026-06-05 14:30`.\n\n**Dual metadata rule:** The file header contains the SAME metadata twice:\n1. As YAML comments (`# key: value`) — for human readers\n2. As YAML key:value pairs — for machine parsing\nBoth must match exactly. Do NOT skip either form.\n\n**Complete file template:**\n\n```yaml\n# generated: 2026-06-05 14:30\n# last_updated: 2026-06-05 14:30\n# project: {project_name}\n# project_key: NOKEY\n# tracking_system: file-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# 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\ngenerated: 2026-06-05 14:30\nlast_updated: 2026-06-05 14:30\nproject: {project_name}\nproject_key: NOKEY\ntracking_system: file-system\nstory_location: {story_location}\n\ndevelopment_status:\n  epic-1: backlog\n  1-1-user-authentication: backlog\n  1-2-account-management: backlog\n  epic-1-retrospective: optional\n  epic-2: backlog\n  2-1-personality-system: backlog\n  epic-2-retrospective: optional\n```\n\n**Key format rules (EXACT — do not deviate):**\n\n| Item type | Pattern | Example |\n|-----------|---------|---------|\n| Epic | `epic-{N}` | `epic-1`, `epic-2` |\n| Story | `{N}-{M}-{kebab-title}` | `1-1-user-authentication`, `2-1-personality-system` |\n| Retrospective | `epic-{N}-retrospective` | `epic-1-retrospective` |\n\nStory key conversion from epic file:\n1. Take the story header: `### Story 1.1: User Authentication`\n2. Replace the period with a dash: `1-1`\n3. Convert the title to kebab-case (lowercase, spaces → hyphens, remove special chars): `user-authentication`\n4. Combine: `1-1-user-authentication`\n\n**Status rules (per item type — NEVER mix):**\n\n| Item type | Valid statuses | Default for new items |\n|-----------|---------------|----------------------|\n| Epic | `backlog`, `in-progress`, `done` | `backlog` |\n| Story | `backlog`, `ready-for-dev`, `in-progress`, `review`, `done` | `backlog` |\n| Retrospective | `optional`, `done` | `optional` |\n\n**Ordering rule:** Items MUST appear in this sequence: epic-N, all its stories in story-number order, epic-N-retrospective, then epic-(N+1), etc.\n\n**Sprints section (OPTIONAL):**\n\nOnly add `sprints:` if you are explicitly grouping stories into named sprints. If unsure, omit it entirely.\n\n```yaml\nsprints:\n  sprint_1:\n    goal: \"MVP core features\"\n    start_date: \"2026-06-01\"\n    end_date: \"2026-06-14\"\n    stories:\n      - epic-1\n      - 1-1-user-authentication\n      - 1-2-account-management\n      - epic-1-retrospective\n```\n\nEvery key in a sprint's `stories` list MUST exist in `development_status`.\n\n\u003Caction>Write the complete sprint status YAML to {status_file}\u003C\u002Faction>\n\u003Caction>CRITICAL: Do NOT add any top-level fields not listed above (no version, no notes, no summary, no health, no velocity)\u003C\u002Faction>\n\u003Caction>CRITICAL: Do NOT use camelCase field names — use exactly snake_case as shown\u003C\u002Faction>\n\u003Caction>CRITICAL: Do NOT use legacy status aliases \"drafted\" or \"contexted\" — use the canonical forms\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},"main","473351382920a74eb8f353f979a06f6f05bb5f59","resources\u002F_aac\u002Fskills\u002Faac-sprint-planning",0,"https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt","https:\u002F\u002Fgithub.com\u002Fmsayedshokry","2026-08-29 02:00:07",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add msayedshokry\u002FAgileAgentCanvasExt --skill aac-sprint-planning",{"tool":49,"command":50},"bunx","bunx skills add msayedshokry\u002FAgileAgentCanvasExt --skill aac-sprint-planning",{"tool":52,"command":53},"pnpm","pnpm dlx skills add msayedshokry\u002FAgileAgentCanvasExt --skill aac-sprint-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-sprint-planning\u002FSKILL.md",true,[57,63,69],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"checklist.md","REFERENCE","参考文档",2028,"https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-sprint-planning\u002Fchecklist.md",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"customize.toml","OTHER","其他",1605,"https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-sprint-planning\u002Fcustomize.toml",{"path":70,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":71,"sourceHtmlUrl":72},"sprint-status-template.yaml",1740,"https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-sprint-planning\u002Fsprint-status-template.yaml",[74,102,120,133,155,171],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":90,"publishedAt":31},"01M6DNRTHE3M1XG3KDJTEF6BG6","bmad-teach-me-testing","Teach testing progressively through structured sessions. Use when user says \"lets learn testing\" or \"I want to study test practices\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Fbmad-teach-me-testing\u002FSKILL.md",[80,85],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[91,92,93,94,95,96,97,98,99,28,30,100,101],"bmad","me","bmad teach me testing","teach me","teach","testing","test","sessions","learn","study","structured",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":109,"publishedAt":31},"01M6DNRG27V77JEGMPMJVRY0Q5","aac-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\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-trace\u002FSKILL.md",[108],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[110,111,97,112,113,24,114,115,116,28,117,30,118,119],"aac testarch trace","trace","quality gate","create","analyze","quality","decision","coverage","test coverage","gate",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":127,"publishedAt":31},"01M6DNR70G1S0DGDSHRWT1S1DD","aac-testarch-test-review","Review test quality using best practices validation. Use when user says \"lets review tests\" or \"I want to evaluate test quality\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-test-review\u002FSKILL.md",[126],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[128,129,97,130,131,115,28,30,132],"review","aac testarch test review","best practices","validation","tests",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":146,"publishedAt":31},"01M6DNQXV8F40EE78ZMWGWRPJM","aac-testarch-test-design","Create system-level or epic-level test plans. Use when the user says \"lets design test plan\" or \"I want to create test strategy\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-test-design\u002FSKILL.md",[139,140,143],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},{"categoryNo":141,"categoryName":142,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":144,"categoryName":145,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000032","设计师",[147,148,97,149,28,113,150,26,151,152,30,153,154],"aac testarch test design","test design","design","test plan","system","strategy","test strategy","plans",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":31},"01M6DNQNG0T7Q5DKV3C03RY35D","aac-testarch-nfr","Audit NFR evidence for performance, security, reliability, and scalability. Use when implementation evidence exists and the user says \"audit NFR evidence\", \"audit NFRs\", or \"evaluate non-functional requirements\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-nfr\u002FSKILL.md",[],[162,163,164,165,166,167,28,168,169,30,170],"aac testarch nfr","reliability","evidence","implementation","scalability","requirements","audit","performance","security",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":178,"publishedAt":31},"01M6DNQDPTGB49D8AAJV4GN2H8","aac-testarch-framework","Initialize test framework with Playwright or Cypress. Use when the user says \"lets setup test framework\" or \"I want to initialize testing framework\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-framework\u002FSKILL.md",[177],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[179,180,181,28,30,182,183,184,97,185,96,186],"aac testarch framework","framework","initialize","testing framework","setup","test framework","playwright","cypress"]