bmad-sprint-planning

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

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/unbakedcosmos/thumbnailer --skill bmad-sprint-planning-unbakedcosmos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/unbakedcosmos/thumbnailer/tree/main/.claude/skills/bmad-sprint-planning
Command: npx skills add https://github.com/unbakedcosmos/thumbnailer --skill bmad-sprint-planning-unbakedcosmos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agile teams using file-based planning lose track of which epics and stories are backlog, in-progress, or done. This Skill automates the creation and maintenance of a sprint-status.yaml file so sprint tracking stays synchronized with the actual epic documents and story files on disk. ## Core Features & Use Cases - Epic and Story Parsing: Scans epic markdown files (whole or sharded) and extracts every epic, story, and retrospective entry with kebab-case keys. - Intelligent Status Detection: Upgrades stories to ready-for-dev when story files exist, preserves more advanced existing statuses, and never downgrades progress. - Validated YAML Output: Produces a structured sprint-status.yaml with documented status state machines, ordered entries, and carried-over retrospective action items. - Use Case: After writing epics for a new product, run sprint planning to instantly generate a complete tracking file that developers and agents update as work progresses. ## 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 workflow, which scans all files matching the epic pattern in your planning artifacts directory, extracts epics and stories, and writes a complete sprint-status.yaml with detected statuses.

How does sprint status detection work with story files?▼

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

Can sprint planning handle sharded epic documents?▼

Yes. If no whole epic file exists, the workflow reads the sharded index.md and all referenced epic section files, combining them for complete coverage. Whole documents take priority when both forms exist.

Will regenerating sprint status overwrite completed story progress?▼

No. The workflow never downgrades statuses, so a story marked done stays done. Existing action_items sections from retrospectives are also carried over unchanged into the regenerated file.

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

Epics flow backlog to in-progress to done. Stories flow backlog, ready-for-dev, in-progress, review, then done. Retrospectives toggle between optional and done, and action items move from open to in-progress to done.