Verified:GitHub

bmad-sprint-status

Summarize sprint progress and detect delivery risks from sprint-status.yaml.

36|16|Updated May 1, 2026

Search Tags:#workflow orchestration #software delivery #project tracking #backlog management #sprint status #risk detection

Ready to run

npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-sprint-status-tronghieu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-sprint-status
Source: https://github.com/tronghieu/lumina-wiki/tree/main/.agents/skills/bmad-sprint-status
Command: npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-sprint-status-tronghieu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a structured sprint status file into a clear sprint snapshot by summarizing progress and highlighting risks that could block delivery.

Core Features & Use Cases

Sprint visibility summary: Reads sprint-status.yaml and reports counts for story, epic, and retrospective states.
Risk surfacing: Detects staleness, orphaned items, review/in-progress gaps, and suggests likely next workflow moves.
Next-step recommendation: Chooses the highest-priority next workflow action based on current statuses, so you know what to run next.

Quick Start

Ask your agent to check sprint status (for example: “show sprint status”) to get a summarized view plus a recommended next workflow command.

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 progress and surface delivery risks from a status file?▼

To summarize sprint progress, you can use an agent to read a structured sprint-status.yaml file. It validates states, computes counts for stories and epics, detects anomalies like staleness, and outputs a recommended next workflow.

What types of delivery risks can be detected during sprint execution?▼

Sprint risk detection identifies staleness, orphaned items, and review or in-progress gaps within your workflow. It analyzes sprint metadata and status values to highlight issues that could block software delivery.

How do I track sprint status for epics, stories, and retrospectives across multiple states?▼

Sprint status tracking works by loading sprint metadata and validating status values from a structured yaml file. It computes counts for story, epic, and retrospective states to provide a clear sprint snapshot.

Can I get a recommended next workflow action based on current sprint statuses?▼

Yes, sprint status analysis chooses the highest-priority next workflow action based on current statuses. It evaluates workflow customization and output a recommended next workflow command for sprint planning or daily execution.

Do I need a specific file format to track sprint backlog and project status?▼

Yes, sprint tracking requires a structured sprint-status.yaml file. The workflow reads this file to validate status values, resolve workflow customization, and compute counts for stories and epics across multiple status states.