bmad-sprint-planning

To generate sprint status tracking from BMAD epic markdown files, the Skill parses epic numbers, story IDs, and titles, then outputs a complete sprint-status.yaml file. It validates the results against the workflow state machine to ensure accurate epic, story, and retrospective coverage.

Story status detection works by locating existing story files and promoting their statuses appropriately. It preserves any more advanced status already recorded in the file, ensuring no progress is lost during deterministic YAML generation and workflow state machine validation.

Yes, you can use this for local Jira-like planning workflows without external dependencies. The Skill operates independently to apply complete epic, story, and retrospective coverage across your planning and implementation folders using only your local markdown files.

The best way to maintain consistent sprint tracking keys is using deterministic key generation. The Skill extracts epic numbers and story IDs from markdown artifacts to produce uniform keys, ordering them validation-friendly within the sprint-status.yaml output.

Sprint planning requires validation against a workflow state machine to ensure story statuses transition correctly and maintain integrity. This validation prevents invalid status overrides during status preservation and guarantees the sprint-status.yaml reflects accurate project delivery progress.

The sprint planning Skill outputs a sprint-status.yaml format containing epics, stories, retrospectives, and metadata. This YAML output provides a complete sprint board snapshot structured with validation-friendly ordering for planning, execution, and progress review.