bmad-sprint-planning

Generates and validates sprint-status.yaml tracking files from epic planning documents.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-sprint-planning-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-sprint-planning
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-sprint-planning-hordricjr

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 planning documents and implementation drift apart. This Skill gates planning readiness, generates a sprint-status.yaml tracking file from epic documents, summarizes progress, and repairs broken tracking files. ## Core Features & Use Cases - Readiness Gate: Audits planning artifacts (PRDs, architecture, epics) and returns a PASS/CONCERNS/FAIL verdict on whether the plan is implementable before any code is written. - Deterministic Tracking Generation: Parses epic files into a structured sprint-status.yaml via a Python script that preserves existing statuses, never downgrades progress, and normalizes legacy status values. - Status, Validation, and Repair: Summarizes sprint progress with risks and next recommended actions, validates file structure, and rebuilds corrupted tracking files with user-confirmed evidence. - Use Case: After writing epics for a new product, ask the AI to run sprint planning; it checks readiness, generates sprint-status.yaml, and later answers "where are we" with counts, risks, and the next story to build. ## Quick Start Ask the AI 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 and Story headings from your epic markdown files and writes sprint-status.yaml with backlog defaults. Stories with files on disk are automatically floored to ready-for-dev, and existing statuses are preserved.

How do I check if my project 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 requirements trace into stories and that no decisions are left unrecorded.

Can I validate or fix 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 the script overwrite existing story statuses when regenerating?

No. The generate command merges with the existing file and never downgrades statuses; it preserves advanced statuses, action items, and custom keys. Legacy v6 values like drafted are normalized to their modern equivalents.

What happens when sprint planning runs in headless mode?

Headless mode skips interactive questions, runs the readiness gate, and generates tracking automatically. Ambiguities that would normally prompt the user halt with a blocked status, and the run ends with a structured JSON response.