bmad-sprint-planning

To generate a sprint-status.yaml from epic markdown files, you run sprint planning to parse whole or sharded epics, convert story headings into kebab-case keys, and validate the output. This automates manual tracking by detecting file existence to set readiness.

Sprint planning can automatically detect story readiness from the file system by checking for the existence of story implementation files. It uses this detection to set readiness statuses while preserving any existing higher statuses in the sprint-status.yaml.

The best way to track sprint progress without hand-editing files is to parse epic markdown documents and convert story headings into kebab-case keys. This process produces an ordered, validated sprint-status.yaml with embedded metadata comments.

Sprint planning works with sharded epic documents by parsing the fragmented files to extract epic numbers and story IDs. It consolidates these parsed elements into a single canonical sprint-status.yaml file for the team.

Converting story headings to kebab-case keys improves sprint tracking by standardizing story identifiers within the sprint-status.yaml. This ensures consistent naming, prevents manual keying errors, and allows automated validation checks for correct status values.

Running sprint planning will not overwrite existing higher statuses in the yaml file. The process preserves existing higher statuses while updating readiness based on file existence, ensuring no manual progress tracking is lost during regeneration.