bmad-sprint-status

Summarizes sprint statuses from sprint-status.yaml and recommends the next BMAD workflow action.

Updated May 17, 2026
One-click install
npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill bmad-sprint-status-thuantan2060
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-status
Source: https://github.com/thuantan2060/facebook-sale-tracking/tree/main/.agents/skills/bmad-sprint-status
Command: npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill bmad-sprint-status-thuantan2060

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It turns your sprint-status.yaml into an actionable sprint snapshot by summarizing progress, validating status values, and surfacing risks that could block delivery.

Core Features & Use Cases

  • Sprint visibility: Counts stories and epics by lifecycle stage and highlights what is actually moving.
  • Risk surfacing: Detects staleness, review/in-progress bottlenecks, orphaned stories, and mismatched epic/story relationships.
  • Next-workflow recommendation: Suggests the highest-priority next BMAD workflow based on the current status distribution.
  • Interactive correction: Flags unknown status values and lets you update the file to proceed safely.
  • Use case: When sprint execution stalls or drifts, this Skill quickly tells you what to do next (code review, dev, create story, or retrospective) and why.

Quick Start

Ask for sprint status and run bmad-sprint-status to get a concise summary with risks and 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 get a clear sprint status summary from a yaml file?

Sprint status summary tools parse your sprint-status.yaml file, count story and epic states, and surface delivery risks like bottlenecks or orphaned items to provide an actionable snapshot.

How does agile tracking detect sprint risks and stale updates?

Agile tracking detects sprint risks by validating metadata fields and applying rules to identify staleness, review bottlenecks, and orphaned stories that could block workflow delivery.

How do I determine the next BMAD workflow action for an active sprint?

To determine the next BMAD workflow action, the system analyzes your current status distribution and recommends the highest-priority step, such as code review, dev, or retrospective.

What should I do when sprint execution stalls with unknown status values?

When sprint execution stalls with unknown status values, you should run an interactive correction process that flags invalid metadata and lets you update the file safely before proceeding.

Does workflow orchestration require specific metadata fields for code review readiness?

Yes, workflow orchestration requires parsing known status values and validating specific metadata fields in your sprint-status.yaml to accurately assess code review readiness.

Can I identify orphaned stories and mismatched epic relationships during a sprint check-in?

Yes, you can identify orphaned stories and mismatched epic relationships during a sprint check-in by applying risk detection rules to your parsed sprint status metadata.