bmad-sprint-planning

The sprint planning workflow automates sprint-status.yaml generation by scanning project directories for epic and story markdown files, parsing headers and sections to extract epics and stories, and outputting an ordered YAML tracking file with inferred statuses.

Status inference works by detecting existing story artifact files in the project directory to upgrade story statuses. The workflow preserves advanced statuses found in an existing sprint-status.yaml and validates all transitions against a defined state machine.

Yes, sprint planning automation works with sharded epic files. The workflow scans project planning artifacts for both whole and sharded epic files, building a complete inventory of epics and stories regardless of file distribution across the repository.

The best way to maintain sprint progress tracking without manual reconciliation is to run an automated sprint planning workflow that discovers epics and stories from markdown files, infers statuses from artifacts, validates YAML output, and reports summary metrics for planning reviews.

Yes, sprint-status.yaml generation performs both coverage and YAML validation checks. The workflow validates the output against a defined state machine, ensuring all stories are accounted for and the YAML structure is correct before reporting summary metrics for planning reviews.

When you regenerate sprint-status.yaml, the workflow preserves any existing advanced statuses found in the current file. It detects story artifact files to upgrade statuses while ensuring previously set advanced statuses are retained during the automated update.