bmad-sprint-status

To generate a sprint status summary, you need a sprint-status.yaml file containing your epics, retrospectives, and stories. This skill parses that file to aggregate current progress, validate item statuses, and display a clear summary of your sprint.

You can identify sprint risks by analyzing your sprint-status.yaml file for stalled stories, stale data, or orphaned tasks. This skill proactively surfaces these potential issues and flags them so Scrum Masters can address them quickly.

The best way to recommend the next agile workflow action is to evaluate current sprint progress and risks. This skill prioritizes subsequent tasks, suggesting logical steps like starting a story, reviewing code, or creating a new task.

Yes, you can use this skill to validate epic and story statuses for your development team. It classifies items within the sprint-status.yaml file, checks their current states, and ensures your sprint data is accurate and up to date.

Yes, you need a sprint-status.yaml file to check scrum sprint progress and surface risks. This skill depends entirely on the structured data within that yaml file to classify items, identify issues, and recommend next steps.

Your sprint status report shows stale data or orphaned tasks when items in the sprint-status.yaml file are not updated or lack proper parent linkage. This skill proactively detects these risks to help you maintain accurate sprint tracking.