bmad-sprint-planning

Sprint planning automation works by reading your epic and story definitions, detecting current statuses, and writing a deterministic sprint-status.yaml file. This machine-readable artifact preserves existing progress and ensures consistency across the agile project.

Sprint status tracking handles existing progress by reading planning artifacts, detecting current statuses for epics and stories, and preserving that progress in the generated sprint-status.yaml file. This ensures continuity and consistency across the sprint plan.

You can automate sprint planning by feeding epic and story definitions into this Skill, which reads the planning artifacts and derives a complete sprint-status.yaml. It automatically detects statuses for epics, stories, and retrospectives to ensure full sprint plan consistency.

Tracking retrospectives in a YAML sprint plan is best handled by deriving them from epic files. This Skill detects retrospective statuses alongside epics and stories, writing a deterministic sprint-status.yaml that ensures consistency and provides a machine-readable artifact for audits.

Automated sprint planning requires epic and story definitions to be stored as planning artifacts that the Skill can read. It processes these files to derive statuses and generate a machine-readable sprint-status.yaml, preserving existing progress while ensuring consistency across the sprint plan.

Using a YAML file for sprint planning provides a deterministic, machine-readable artifact that is suitable for audits and team alignment. The generated sprint-status.yaml tracks epics, stories, and retrospectives, preserving existing progress while ensuring consistency across the sprint plan.