bmad-sprint-planning

To generate sprint status from epic definitions, this skill parses markdown files of your epics and stories, detects story file existence to assign initial statuses, and produces a valid sprint-status.yaml file.

The best way to track sprint progress using markdown files is by parsing epic definitions and detecting story file existence to automatically update and preserve existing progress in a sprint-status.yaml file.

Yes, sprint status tracking requires a structured input of epics and stories defined in markdown files, ensuring the workflow can detect file existence and map all work items comprehensively to a sprint-status.yaml file.

Yes, you can preserve existing story statuses when updating the sprint-status.yaml file, because the workflow detects existing progress and only assigns initial statuses to newly identified stories during the markdown parsing process.

Automated epic management detects the current status of stories by checking for the existence of corresponding story files within your project structure during the parsing phase of the sprint planning workflow.