bmad-sprint-status

To generate an agile sprint status summary, load your project context and sprint-status.yaml data. The workflow validates statuses, computes counts for stories and epics, detects timing and dependency risks, and recommends the next workflow action.

Surfacing sprint risks during standups requires reading sprint-status.yaml to detect timing issues, dependency risks, stale data, and orphaned stories. This workflow aggregates the data into a concise snapshot for quick stakeholder decisions.

Tracking orphaned stories and stale data involves loading configuration from _bmad/bmm/config.yaml and validating sprint-status.yaml entries. The workflow automatically detects these issues and flags them as risks in the status summary.

Yes, you can use sprint-status.yaml to recommend next actions for sprint planning. The workflow evaluates story and epic statuses to suggest specific next steps like dev-story, code-review, or create-story.

The sprint status workflow requires the _bmad/bmm/config.yaml file to load project configuration, alongside the sprint-status.yaml file. It uses these inputs to validate statuses and compute the current sprint snapshot.

You should not use an automated sprint status summary if your project lacks a structured sprint-status.yaml file or valid configuration. The workflow depends on these specific files to accurately validate statuses, detect risks, and recommend next steps.