bmad-sprint-status

To summarize sprint status from YAML, this tool parses sprint-status.yaml and classifies stories and epics across backlog, in-progress, review, and done categories to detect risks like stale data or orphaned stories. It then produces a concise sprint health summary with recommended next actions.

Automated agile workflows can detect sprint anomalies such as stale data, orphaned stories, and in-progress epics containing no active stories. By enforcing valid status values across parsed YAML artifacts, the system flags these risks and returns a recommended next workflow for automation.

Generating a sprint health summary requires loading sprint-status.yaml to aggregate counts across backlog, ready-for-dev, in-progress, review, and done categories. The process evaluates both epics and stories to output a risk-aware next-step recommendation.

Yes, you can extract a recommended next workflow ID directly from sprint-status YAML. The parser evaluates sprint health across story categories and returns both a next_workflow_id and a next_story_id to drive automated agile project workflows.

Yes, this sprint status tool operates without external dependencies. It directly ingests sprint-status.yaml files to classify stories, enforce valid status values, and generate risk-aware summaries for agile project workflows.

The best way to automate sprint risk detection is parsing sprint-status.yaml to identify in-progress epics with no active stories. This approach flags orphaned stories and stale data, returning a recommended next workflow ID for automated next-step execution.