bmad-sprint-status

To summarize sprint status and identify risks, you can parse the sprint-status.yaml file to count story statuses and detect blockers. This provides a concise health snapshot and recommended next workflow actions.

The best way to track sprint risks for daily standups is by analyzing development_status data to surface blockers and priority areas. It generates a concise summary and recommends next workflow actions to guide team discussions.

You generate a sprint health snapshot for review meetings by reading project configuration and parsing development_status counts. This aggregates story and epic statuses to highlight priority areas for action.

Yes, this sprint status workflow requires a specific project directory structure. It reads configuration from the {project-root}/_bmad/bmm/config.yaml file and parses the sprint-status.yaml file to function correctly.

Sprint status detection works by reading development_status entries and counting statuses across epics and stories. It then applies this parsed data to recommend relevant next workflow actions for sprint planning and review meetings.