bmad-sprint-status

You can summarize sprint status by parsing a sprint-status.yaml file to classify current states, detect stalled epics or overdue items, and output recommended next actions for stakeholders.

Using a status yaml file, you can automate sprint planning, daily standups, and risk assessments by extracting current states and generating workflow recommendations for code review or development.

To detect stalled epics and overdue items, the sprint workflow parses your status data to identify mismatched statuses and surfaces these risks to inform your next actions.

Yes, this sprint risk assessment tool applies to daily standups by parsing your sprint-status.yaml, classifying task progress, and providing clear actionable next steps for the team.

Yes, you need a sprint-status.yaml file format to track sprint health, as the tool parses this specific structured data to extract current states and surface project risks.

The best way to generate actionable next steps for dev and code review is to parse sprint status data, classify task progress, and surface mismatched statuses to recommend workflow actions.