bmad-sprint-status

Summarize sprint status and flag risks from sprint-status.yaml data.

Updated May 5, 2026

Search Tags:#workflow #agile #status #sprint #risk #project-management

Ready to run

npx skills add https://github.com/b566776/whitebox --skill bmad-sprint-status-b566776

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically summarizes sprint status, surfaces risks, and recommends the next actions to keep software delivery on track.

Core Features & Use Cases

Parse the sprint-status.yaml to categorize stories, epics, and retrospectives and provide a unified view.
Detect risks such as stale data, orphaned stories, and in-progress epics with no associated stories.
Recommend the next workflow action (e.g., dev-story, code-review, create-story) and present a concise, decision-ready summary.
Ideal for sprint planning, standups, and retrospective preparation to quickly align teams.

Quick Start

Run the sprint-status workflow to generate a concise status summary and recommended next action for the current sprint.

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 status and surface risks from agile project data?▼

To summarize sprint status and surface risks, you can use a workflow that parses a sprint-status.yaml file to categorize stories, epics, and retrospectives. It validates metadata, flags issues like orphaned stories, and outputs a decision-ready summary with recommended next actions.

What sprint risks should I look for during agile project management?▼

Common sprint risks to look for include stale data, orphaned stories, and in-progress epics with no associated stories. An automated workflow can detect these risks by validating metadata and parsing your sprint configuration to provide a unified risk overview.

How do I track agile stories and epics for sprint planning and standups?▼

You track agile stories and epics by parsing a sprint-status.yaml file to categorize them alongside retrospectives. This provides a unified view that validates metadata and classifies progress, making it ideal for aligning teams during sprint planning, standups, and retrospective preparation.

Can I get recommended next workflow actions based on current sprint data?▼

Yes, you can get recommended next workflow actions based on current sprint data. By classifying stories and epics, the workflow analyzes progress and suggests specific next actions like dev-story, code-review, or create-story to keep software delivery on track.

Do I need a sprint-status.yaml file to monitor project risks and progress?▼

Yes, you need a sprint-status.yaml file to monitor project risks and progress. The workflow relies on parsing this specific configuration file to load settings, validate metadata, categorize items, and output a concise status summary for agile development teams.

What is the best way to prepare a decision-ready sprint status summary?▼

The best way to prepare a decision-ready sprint status summary is to automate parsing your sprint data to categorize stories, epics, and retrospectives. This approach validates metadata, surfaces risks like stale data, and presents a concise summary with recommended next actions.