bmad-sprint-status

Summarize sprint progress from sprint-status.yaml and recommend the next workflow step.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-sprint-status-enigmaicon-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-status
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/BMAD-METHOD/src/bmm-skills/4-implementation/bmad-sprint-status
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-sprint-status-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns your sprint status file into an actionable summary, surfacing risks and recommending what to do next so teams don’t drift or miss critical blockers.

Core Features & Use Cases

  • Sprint visibility from sprint-status.yaml: Reads and validates sprint metadata, including story/epic/retrospective status.
  • Risk detection and guidance: Flags staleness, orphaned items, review blockers, and “stuck” progress patterns.
  • Next-workflow recommendation: Selects the highest-priority next step (e.g., dev-story, code-review, create-story) and offers follow-up actions.
  • Operational safety checks: Validates status values and can prompt for corrections when unknown statuses are found.

Quick Start

Tell your agent: "Check sprint status and recommend the next workflow action."

Frequently Asked Questions about bmad-sprint-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize sprint status from a yaml file?

To summarize sprint status from a yaml file, you can use a workflow orchestration tool that parses sprint-status.yaml, computes story and epic counts, and generates an actionable progress summary.

What is agile risk detection for software delivery workflows?

Agile risk detection for software delivery workflows is the process of identifying staleness, orphaned items, and review blockers in sprint tracking to surface critical issues before they derail progress.

How do I validate sprint status values in a yaml file?

You validate sprint status values in a yaml file by applying deterministic parsing rules that check known status values and prompt for corrections when unknown statuses are found.

Can I use sprint tracking yaml validation for next-step planning?

Yes, sprint tracking yaml validation supports next-step planning by selecting the highest-priority workflow identifier, such as dev-story or code-review, based on your project's current status counts.

Why does my sprint status summary show unknown status values?

Your sprint status summary shows unknown status values when the yaml validation encounters statuses outside the defined known values, triggering operational safety checks to prompt for corrections.