bmad-sprint-planning

Generates sprint-status.yaml tracking files by parsing epic and story markdown documents.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/5onyy/essential-ai-agent-skills --skill bmad-sprint-planning-5onyy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/5onyy/essential-ai-agent-skills/tree/main/.cursor/skills/bmad-sprint-planning
Command: npx skills add https://github.com/5onyy/essential-ai-agent-skills --skill bmad-sprint-planning-5onyy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agile teams lose track of which epics and stories are in backlog, in progress, or done when planning artifacts live only in markdown files. This Skill automatically builds a structured sprint-status.yaml from your epic documents so development progress is tracked in one canonical file. ## Core Features & Use Cases - Epic and Story Parsing: Discovers whole or sharded epic markdown files and extracts every epic, story, and retrospective entry. - Intelligent Status Detection: Upgrades story status to ready-for-dev when a matching story file exists, and never downgrades existing statuses. - Validated YAML Output: Generates a sprint-status.yaml with defined status state machines (backlog, in-progress, review, done) and runs completeness checks against the source epics. - Use Case: After writing epics for a new product, ask the agent to run sprint planning and receive a complete sprint-status.yaml listing every epic, story, and retrospective with detected statuses. ## Quick Start Run sprint planning to generate the sprint status file from my 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 markdown documents?▼

Run the sprint planning workflow, which scans your planning artifacts directory for files matching the epic pattern, extracts all epics and stories, and writes a sprint-status.yaml with detected statuses to your implementation artifacts folder.

How does sprint status detection work for stories?▼

The workflow checks whether a story markdown file exists in the story location for each parsed story. If the file exists, the story status upgrades from backlog to at least ready-for-dev, while existing more advanced statuses are preserved.

Can I use sharded epic files split across multiple markdown documents?▼

Yes. If no whole epic document is found, the workflow reads the epics index.md and loads every listed epic section file, combining them for complete sprint status coverage. Whole documents take priority when both exist.

What statuses can epics and stories have in sprint-status.yaml?▼

Epics move through backlog, in-progress, and done. Stories flow through backlog, ready-for-dev, in-progress, review, and done. Retrospectives toggle between optional and done.

Why are stories missing from my generated sprint-status.yaml?▼

Missing stories usually mean the epic files were not found under the configured planning artifacts path or the story headers do not follow the expected Story X.Y format. Check the epics pattern and file naming, then re-run the workflow.