skills.rest
mschuerig
mschuerigCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bmad-sprint-status

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

Updated Feb 11, 2026
Search Tags:#workflow#planning#agile#status#sprint#risk
One-click install
npx skills add https://github.com/mschuerig/peach-ios --skill bmad-sprint-status-mschuerig
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-sprint-status
Source: https://github.com/mschuerig/peach-ios/tree/main/_bmad/bmm/workflows/4-implementation/bmad-sprint-status
Command: npx skills add https://github.com/mschuerig/peach-ios --skill bmad-sprint-status-mschuerig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint health is often hidden behind scattered updates and conflicting statuses. This Skill consolidates status data to surface risks, blockers, and actionable next steps, reducing ambiguity and speeding decision-making.

Core Features & Use Cases

  • Summarizes sprint status across epics and stories from the sprint-status data.
  • Detects risks and blockers early and recommends concrete follow-up actions.
  • Guides sprint planning and retrospective discussions with clear, actionable insights.

Quick Start

Run the sprint-status workflow to generate a status summary and recommended next actions.

Frequently Asked Questions about bmad-sprint-status

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

FAQPage Schema
How do I assess sprint health and surface risks from scattered agile updates?▼

Assess sprint health by consolidating status data to surface risks, blockers, and actionable next steps. This approach reduces ambiguity from conflicting statuses and speeds up decision-making for agile teams.

How do I summarize sprint status across epics and stories?▼

Summarize sprint status by loading configuration data from a sprint-status file to validate progress across epics and stories. This workflow automatically detects risks and recommends concrete follow-up actions.

What is the best way to detect blockers and guide sprint planning discussions?▼

Detect blockers by running an automated sprint-status workflow that highlights risks early. This generates clear, actionable insights to guide sprint planning and retrospective discussions effectively.

Can I use a YAML file to track sprint progress and validate agile status?▼

You can use a sprint-status.yaml file to track progress, epics, and stories. The workflow validates this configuration data to ensure guardrails are met and actionable outputs are generated.

Does this sprint status tracking approach work for teams already using agile workflows?▼

This approach works for agile teams needing to surface blockers and guide next steps. It requires no external dependencies, applying configuration loading and risk detection directly to sprint-status data.

Related Skills

Explore More Product & Management Skills→
b566776b566776

bmad-sprint-status

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

Community
Advanced
kay6198835kay6198835

retrospective

Generate structured sprint retrospectives from project data and git history.

Community
Advanced
mcauduro0mcauduro0
1

scrum-master

Analyze sprint data with Monte Carlo simulations to forecast velocity and team health.

Community
Advanced
johnatas-henriquejohnatas-henrique

sprint-status

Aggregate sprint metrics and flag stale tasks from plan and story files.

Community
Intermediate