bmad-sprint-planning

To generate sprint status tracking from epic markdown files, you parse all epics, stories, and retrospectives. This process extracts the planning entries and builds a complete, normalized YAML inventory for progress tracking.

The best way to maintain consistent story status is to use deterministic YAML generation. This approach normalizes story keys and enforces valid workflow transitions, ensuring reliable file-system-based progress tracking across all epics.

Yes, sprint planning YAML generation preserves existing story statuses. The parsing mechanism applies default states to new entries while specifically preserving more advanced existing statuses during the inventory build.

Yes, you can use markdown parsing for sprint planning in repositories with multiple retrospective entries. The parser reads one or many epic files and extracts every epic, story, and retrospective entry into a complete tracking inventory.

Legal state validation matters when generating a sprint-status.yaml file because it enforces valid workflow transitions. This prevents invalid status updates and ensures deterministic, consistent progress tracking across the repository.