skills.rest
mol4
mol4COMMUNITY
Explore all skills by this author →
GitHub

bmad-sprint-status

Summarize sprint progress from sprint-status.yaml and identify risks.

1|Updated Mar 31, 2026
Search Tags:#workflow#epics#jira#stories#bmad#sprint status
One-click install
npx skills add https://github.com/mol4/BMAD-Board --skill bmad-sprint-status-mol4
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-sprint-status
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-sprint-status
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-sprint-status-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It gives teams a fast, reliable view of sprint progress so they can see what is done, what is blocked, and what should happen next.

Core Features & Use Cases

  • Reads sprint-status.yaml and turns raw status data into a concise sprint summary.
  • Normalizes legacy story and epic states, checks for invalid values, and flags risks such as stale files or orphaned stories.
  • Recommends the next BMAD workflow, such as development, code review, story creation, or retrospective.
  • Use it when you need a standup update, a sprint health check, or a quick decision on the next action.

Quick Start

Ask for the sprint status summary for the current BMAD project and include any risks and the next recommended workflow.

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 sprint status summary from sprint-status.yaml?▼

You can generate a sprint status summary by parsing sprint-status.yaml to normalize legacy story and epic states, validate file completeness, and flag risks. The output provides a concise health overview detailing what is done, blocked, and next.

What is the best way to identify sprint risks and blocked stories?▼

The best way to identify sprint risks is to parse status metadata to detect stale files, invalid values, and orphaned stories. This process normalizes legacy states and flags issues, yielding a reliable sprint health check highlighting blocked items.

How do I normalize legacy story and epic states in Jira workflows?▼

To normalize legacy story and epic states, parse sprint-status.yaml to check for invalid values and map them to current BMAD workflow states. This validates file completeness and ensures accurate sprint progress tracking across implementation phases.

Does this sprint health check work with BMAD project epics and retrospectives?▼

Yes, this sprint health check applies to BMAD projects tracking stories, epics, and retrospectives across implementation phases. It reads sprint-status.yaml to validate file completeness and summarize progress for these specific project artifacts.

How do I decide the next BMAD workflow action for my sprint?▼

Deciding the next BMAD workflow action involves analyzing sprint progress and risks to recommend development, code review, story creation, or retrospective. This next step recommendation is based on parsing your current status metadata.

Related Skills

Explore More Software Engineering Skills→
bmad-code-orgbmad-code-org
212

gds-sprint-planning

Generate a structured sprint-status.yaml from epic markdown files.

Official
Advanced
ravensorbravensorb

l3io-pm-sprint-execute

Orchestrate sprint lifecycle stages with BMad subagents and quality gates.

Community
Advanced
Rinzler78Rinzler78
1

bmad-sprint-status

Summarize sprint progress and recommend next workflow actions from sprint-status.yaml data.

Community
Advanced
tygwantygwan
1

sync-fix

Detect and fix inconsistencies across Phase tasks, Sprint backlogs, and progress records.

Community
Basic