bmad-sprint-planning

Validates planning readiness and generates sprint-status.yaml tracking files from epic documents.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-sprint-planning-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/bmad-sprint-planning
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-sprint-planning-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? It closes the gap between planning artifacts and implementation by checking that epics and stories are complete enough to build, then generating and maintaining a sprint-status.yaml file that tracks every epic, story, and retrospective through the development lifecycle. ## Core Features & Use Cases - Readiness Gate: Audits planning artifacts (PRDs, architecture, epics) and returns a PASS, CONCERNS, or FAIL verdict before any code is written. - Deterministic Tracking Generation: Parses epic files into kebab-case keys, merges with existing statuses without downgrades, and writes sprint-status.yaml atomically via a Python script. - Status, Validate, and Repair: 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, ask the assistant to run sprint planning; it checks implementability, generates the tracking file, 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 epics.

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 markdown files?

Run the sprint planning flow, which parses Epic and Story headings from your epic files into kebab-case keys and writes sprint-status.yaml. The bundled sprint_plan.py script handles parsing, ordering, merging with existing statuses, and atomic writes.

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

Use the readiness intent, which inventories planning artifacts and judges whether a developer could implement the epics without inventing unrecorded decisions. It returns a PASS, CONCERNS, or FAIL verdict with findings ordered by severity.

Can I validate or repair a broken sprint-status.yaml file?

Yes. The validate subcommand reports structural problems without writing, and the fix flow rebuilds the file by gathering evidence from epics, story files, and git history, then regenerating it after your confirmation.

Does sprint planning overwrite existing story statuses?

No. The generate command merges with the existing file and never downgrades statuses; legacy v6 values like drafted and contexted are normalized to their modern equivalents. Only the explicit fix flow with --set can downgrade, after user confirmation.

What happens when the sprint planning script fails?

The skill instructs the agent to read the files directly, deliver the same outcome by best judgment, explain why the deterministic path failed, and offer the fix flow to restore a file the script can handle.