skills.rest
tuanpa-nhg-eng
tuanpa-nhg-engCOMMUNITY
Explore all skills by this author →
GitHub

bmad-sprint-planning

Generate and maintain sprint-status.yaml tracking files from epic planning documents.

Updated Jul 2, 2026
Search Tags:#workflow automation#epics#agile#yaml#sprint planning#status tracking#readiness gate
One-click install
npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-sprint-planning-tuanpa-nhg-eng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/tuanpa-nhg-eng/nhg-ipms/tree/main/.claude/skills/bmad-sprint-planning
Command: npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-sprint-planning-tuanpa-nhg-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ruamel.yaml, and includes scripts (resource) and references (resource) components.

What problem does it solve? Agile teams lose track of which epics and stories are done, in progress, or blocked when sprint state lives only in scattered planning documents. This Skill gates planning readiness, then generates and maintains a single sprint-status.yaml file that tracks every epic, story, retrospective, and action item. ## Core Features & Use Cases - Readiness Gate: Audits planning artifacts (PRDs, architecture, epics) and returns a PASS, CONCERNS, or FAIL verdict before any tracking is generated. - Deterministic Tracking Generation: Parses epic files into kebab-case story keys, merges with existing statuses without downgrades, detects story files on disk, and writes sprint-status.yaml atomically. - Status, Validate, and Fix Flows: Summarizes sprint progress with risks and next recommended actions, validates file structure, and rebuilds broken tracking files from evidence with user confirmation. - Use Case: After finishing your epics document, ask to run sprint planning; the Skill checks implementability, generates sprint-status.yaml, and later tells you which story to build next. ## Quick Start Ask the assistant to run sprint planning and generate the sprint status file from your epic documents.

Frequently Asked Questions about bmad-sprint-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a sprint status file from epic documents?▼

Run the sprint planning flow, which parses epic files for Epic and Story headings, derives kebab-case keys, and writes sprint-status.yaml via the sprint_plan.py generate subcommand. Existing statuses are preserved and never downgraded during regeneration.

How do I check if my plan is ready for implementation?▼

Use the readiness intent, which inventories planning artifacts like PRDs, architecture, and epics, then returns a PASS, CONCERNS, or FAIL verdict. It checks that stories trace back to recorded decisions and that no required architecture or UX decisions are missing.

What statuses does sprint-status.yaml support?▼

Epics use backlog, in-progress, and done; stories use backlog, ready-for-dev, in-progress, review, and done; retrospectives use optional and done. Legacy v6 values like drafted and contexted are normalized to ready-for-dev and in-progress automatically.

Can I fix a broken or hand-edited sprint-status.yaml file?▼

Yes, the fix flow validates the file, gathers evidence from epic files, story files, and git history, proposes corrected statuses, and rebuilds the file with the generate command using --fresh and --set after your confirmation.

Does sprint planning work in headless or CI mode?▼

Yes, headless mode runs the readiness gate and generates tracking without asking questions, ending with a JSON response containing status, intent, and gate verdict. Ambiguities that would require user input halt with a blocked status instead of guessing.

Related Skills

Explore More Software Engineering Skills→
bacocobacoco
67

bmad-story-planning

Generate developer-ready user stories with acceptance criteria from epics and architecture decisions.

Community
Advanced
LeGeRyChEeSeLeGeRyChEeSe

bmad-dev-story

Implements sprint stories from spec files using a red-green-refactor workflow with status tracking.

Community
Advanced
hanzlahabibhanzlahabib
2

rcode-hussain-sm

Prepare sprint planning, story readiness, and status reports for agile teams.

Community
Advanced
Dev10x-GuruDev10x-Guru
7

Dev10x:jtbd

Draft Job Stories from GitHub and JIRA issue tracker context.

Official
Advanced