bmad-sprint-status

Name: bmad-sprint-status
Availability: InStock
Author: GenEd

Summarizes sprint progress and flags delivery risks from sprint status records.

Updated Mar 30, 2026

Search Tags:#project management #workflow automation #agile #risk analysis #sprint status #yaml validation

Ready to run

npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-sprint-status-geneducation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-sprint-status
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/bmad-sprint-status
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-sprint-status-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives teams a fast, reliable view of sprint progress so they can spot blockers, understand current delivery health, and choose the next best action without manually digging through status files.

Core Features & Use Cases

Sprint Summaries: Condenses story, epic, and retrospective states into a clear status overview.
Risk Surfacing: Flags stale files, orphaned stories, missing stories, and other workflow risks.
Next-Step Guidance: Recommends the most appropriate next BMad workflow based on current sprint conditions.
Use Case: A delivery lead can ask for sprint status before standup and immediately see what is in progress, what needs review, and what workflow should happen next.

Quick Start

Use the bmad-sprint-status skill to review the current sprint, surface risks, 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 summarize sprint progress and identify delivery risks?▼

Summarize sprint progress by condensing story, epic, and retrospective states into a status overview, while identifying delivery risks like stale files and orphaned stories. This validates status metadata and recommends the next BMad workflow action.

What are stale or orphaned stories and how do they affect sprint status?▼

Stale or orphaned stories are sprint items lacking active workflow states or proper epic associations. They affect sprint status by creating delivery risks, which get flagged during status metadata validation to recommend corrective BMad workflow actions.

Can I use this to check sprint status before a daily standup?▼

Yes, you can check sprint status before a standup to see what is in progress, what needs review, and what workflow should happen next. It provides instant summaries and next-step guidance for active sprint tracking.

How do I validate YAML status metadata for agile workflow classification?▼

Validate YAML status metadata by classifying workflow states for stories and epics, flagging missing stories, and identifying orphaned items. This ensures accurate sprint tracking and reliable next-step BMad workflow recommendations.

What is the best way to recommend the next BMad workflow action during sprint planning?▼

Recommend the next BMad workflow action by analyzing current sprint conditions, validating metadata, and surfacing risks like orphaned stories. It identifies the most appropriate workflow step based on real-time epic and story statuses.