bmad-sprint-planning

Sprint status tracking is generated by parsing epic documentation and detecting story progress from repository files to produce a comprehensive sprint-status.yaml file. It resolves workflow configuration and validates development status mapping for consistent sprint execution visibility.

Keeping sprint plans updated requires detecting story readiness by checking for corresponding story files and preserving existing advanced statuses. This approach prevents context drift and maintains alignment by refreshing the sprint-status.yaml after work changes.

Epic-to-sprint status generation parses all epic files, including whole or sharded variants, to extract epic, story, and retrospective entries. It ensures complete coverage by verifying no missing or extra items before writing the tracking file.

Yes, sprint planning workflow automation validates legal state values and checks for valid YAML structure before writing the final tracking file. It applies guardrails to verify coverage and ensure no missing or extra items exist in the sprint plan.

Repository automation for sprint planning preserves existing more-advanced story statuses during status detection. It maps development_status states while checking whether corresponding story files exist, ensuring no progress is lost during context drift or restarts.

Story readiness detection relies on checking whether corresponding story files exist in the repository and mapping development_status states. Limitations include dependency on file presence for status inference and the need for valid epic file formats to ensure complete coverage.