bmad-sprint-planning

This sprint planning workflow reads your epic files, identifies stories, and maps their progress into a complete sprint-status.yaml. It prevents status downgrades while preserving existing higher statuses automatically.

Yes, updating the sprint-status.yaml preserves existing higher statuses. The workflow merges new epic data with your current file, enforcing no downgrades to ensure previously achieved progress remains intact.

Automated sprint planning enforces status transitions by validating consistency between epic definitions and the sprint-status file. It prevents any status downgrade while preserving the highest previously recorded progress.

Yes, the generated sprint-status.yaml is suitable for CI/CD pipelines. It provides a ready-to-use YAML file with structured metadata and validation guidance, serving as a single source of truth for automated dashboards.

The best way to track epic progress in YAML is to generate a sprint-status.yaml file from your epic definitions. This workflow automates status mapping, enforces no downgrades, and produces a validated file for project dashboards.