bmad-sprint-status

To summarize sprint status and surface risks, you can use a workflow that parses a sprint-status.yaml file to categorize stories, epics, and retrospectives. It validates metadata, flags issues like orphaned stories, and outputs a decision-ready summary with recommended next actions.

Common sprint risks to look for include stale data, orphaned stories, and in-progress epics with no associated stories. An automated workflow can detect these risks by validating metadata and parsing your sprint configuration to provide a unified risk overview.

You track agile stories and epics by parsing a sprint-status.yaml file to categorize them alongside retrospectives. This provides a unified view that validates metadata and classifies progress, making it ideal for aligning teams during sprint planning, standups, and retrospective preparation.

Yes, you can get recommended next workflow actions based on current sprint data. By classifying stories and epics, the workflow analyzes progress and suggests specific next actions like dev-story, code-review, or create-story to keep software delivery on track.

Yes, you need a sprint-status.yaml file to monitor project risks and progress. The workflow relies on parsing this specific configuration file to load settings, validate metadata, categorize items, and output a concise status summary for agile development teams.

The best way to prepare a decision-ready sprint status summary is to automate parsing your sprint data to categorize stories, epics, and retrospectives. This approach validates metadata, surfaces risks like stale data, and presents a concise summary with recommended next actions.