bmad-sprint-status

Parse sprint-status.yaml files to summarize statuses and detect risks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually tracking progress across stories, epics, and retrospectatives in BMAD-based development workflows is time-consuming and often leads to missed risks or unclear next steps for the team.

Core Features & Use Cases

  • Sprint Status Summarization: Parses sprint-status.yaml to count and categorize story, epic, and retrospective statuses for a full project overview.
  • Risk Detection: Automatically flags common issues like stale status files, orphaned stories, in-progress epics with no associated stories, and stories stuck in review.
  • Workflow Recommendation: Suggests the next prioritized BMAD workflow action (such as dev-story, code-review, or create-story) based on current sprint state. Use Case: A development team using BMAD can run this skill to instantly get a clear picture of sprint health, identify blockers, and know exactly which workflow to execute next without manually reviewing status files.

Quick Start

Use the bmad-sprint-status skill to check your current sprint status, identify any risks, and get a recommended next workflow action to move your project forward.

Frequently Asked Questions about bmad-sprint-status

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

FAQPage Schema
How do I track sprint progress and detect risks in a BMAD development workflow?

You can summarize sprint status by parsing sprint-status.yaml files to count and categorize story, epic, and retrospective statuses, eliminating manual progress tracking in BMAD-based development workflows.

How do I identify orphaned stories or stale status files in my sprint?

Automated risk detection flags common issues like stale status files, orphaned stories, in-progress epics with no associated stories, and stories stuck in review by validating status values against known enums.

What is the best way to determine the next workflow action for a BMAD sprint?

The best way to determine next workflow actions is using priority-based selection rules that analyze your current sprint state and suggest prioritized BMAD actions like dev-story, code-review, or create-story.

Can I use this sprint tracking skill without the BMAD framework?

No, this skill is specifically designed for development teams using the BMAD framework, as it parses sprint-status.yaml files and validates status values against known BMAD workflow enums.

What format does sprint status data need to be in for automated risk detection?

Automated risk detection requires sprint status data to be in the sprint-status.yaml file format, which the skill parses to validate status values against known enums and identify anomalies.

Why are my epic statuses not reflecting the underlying story progress correctly?

Epic statuses may not reflect story progress if you have in-progress epics with no associated stories or orphaned stories, which the risk detection feature identifies by validating status values against known enums.