bmad-sprint-status

Summarize sprint execution status and identify delivery risks from sprint-status.yaml.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ncptuan/stock_backtest_project --skill bmad-sprint-status-ncptuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-status
Source: https://github.com/ncptuan/stock_backtest_project/tree/main/.claude/skills/bmad-sprint-status
Command: npx skills add https://github.com/ncptuan/stock_backtest_project --skill bmad-sprint-status-ncptuan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly understand current sprint progress without manually inspecting status files, counting story states, or guessing what to do next. It turns a raw sprint tracking file into a clear summary of delivery status, risks, and recommended workflow actions.

Core Features & Use Cases

  • Sprint Status Summary: Reads the sprint-status.yaml file and reports story, epic, and retrospective progress in a compact format.
  • Risk Detection: Flags stale tracking data, invalid statuses, orphaned stories, missing story readiness, and epics that are active without associated stories.
  • Next-Step Recommendation: Suggests the most appropriate follow-up workflow such as development, code review, story creation, or retrospective based on current sprint conditions.
  • Use Case: A developer or delivery lead can ask for sprint status during execution and immediately see what is in progress, what is blocked or risky, and which workflow should be run next.

Quick Start

Ask the assistant to 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 check sprint status and identify delivery risks from a YAML file?

To check sprint status and identify delivery risks, you parse the sprint-status.yaml file to summarize story and epic progress, validate statuses, and flag stale data or orphaned stories. This extracts a clear summary of execution health and risks.

What is the best way to track agile workflow progress without manually counting story states?

Tracking agile workflow progress without manual counting involves summarizing a structured tracking file to automatically classify implementation items, detect edge cases like orphaned stories, and recommend the next development workflow action.

How does risk detection work for active epics without associated stories?

Risk detection for active epics without associated stories works by parsing sprint tracking data, classifying implementation items, and flagging epics that lack linked stories as delivery risks alongside stale planning data and invalid statuses.

Can I get next-action recommendations for my software delivery workflow?

You can get next-action recommendations for your software delivery workflow by analyzing sprint conditions. The system prioritizes follow-up workflows like development, code review, story creation, or retrospective based on current execution status.

Does sprint status tracking work with retrospective and review queue data?

Sprint status tracking works with retrospective and review queue data by parsing these elements from the sprint-status.yaml file. It reports retrospective progress and evaluates review queues to recommend the most appropriate follow-up workflow.

What are the limitations of detecting stale planning data in agile workflows?

Detecting stale planning data in agile workflows is limited to parsing structured sprint-status.yaml files. It cannot identify risks from untracked project data, requiring all story states, epic progress, and review queues to be present in the file.