bmad-sprint-planning

To generate a sprint status YAML file from epic markdown documents, this skill automatically parses both whole and sharded epic files, extracts story IDs, and outputs a validated sprint-status.yaml file with standardized progress tracking keys.

Automated sprint planning detects existing story implementation files to assign initial statuses and preserves manually updated progress from prior sprint tracking files, ensuring completed work is never downgraded during YAML generation.

Yes, you can use this sprint tracking generator with sharded epic file structures, as it automatically parses and extracts all epics and user stories from both whole and sharded markdown files to build the sprint status.

The best way to maintain consistent progress tracking across agile epics is to auto-generate a validated YAML file with embedded status definitions and state machine rules, eliminating manual data entry errors and keeping progress visibility in sync.

You need a BMAD-based agile workflow where epics are defined in markdown files to use this YAML sprint status generation. It applies specifically to BMAD development environments to ensure proper epic and story parsing.

Your generated sprint-status.yaml file includes validation checks and embedded status definitions to enforce state machine rules for progress tracking, ensuring logically ordered entries for epics, stories, and retrospectives remain accurate.