skills.rest
robotics-playground
robotics-playgroundOFFICIAL
Explore all skills by this author →
GitHub

bmad-sprint-status

Analyze sprint-status.yaml to classify stories, epics, and retrospectives and surface risks.

Updated Mar 18, 2026
Search Tags:#workflow#scrum#sprint#risk#project-management#sprint-status
One-click install
npx skills add https://github.com/robotics-playground/skills --skill bmad-sprint-status-robotics-playground
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-sprint-status
Source: https://github.com/robotics-playground/skills/tree/main/_bmad/bmm/workflows/4-implementation/bmad-sprint-status
Command: npx skills add https://github.com/robotics-playground/skills --skill bmad-sprint-status-robotics-playground

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Summarize sprint status and surface risks quickly to improve transparency and reduce manual update toil.

Core Features & Use Cases

  • Aggregates sprint status data from sprint-status.yaml and related project context to present a clear, at-a-glance view of progress.
  • Detects risks such as stale updates, orphaned stories, and in-progress epics with no associated stories, and suggests next steps.
  • Supports Scrum Masters, product teams, and developers in daily standups, sprint planning, and retrospective reviews by providing actionable visibility.

Quick Start

Follow the workflow in workflow.md to run sprint-status reports and recommendations.

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 quick sprint status summary from a yaml file?▼

Sprint status summarization works by analyzing your sprint-status.yaml file to extract current sprint state and risk indicators. It applies project context to classify stories, epics, and retrospectives while computing counts for a human-friendly summary.

What sprint risks are detected during sprint status analysis?▼

Sprint risk detection identifies stale updates, orphaned stories, and in-progress epics with no associated stories. It ensures only recognized statuses are accepted and surfaces recommended next workflows to address these specific vulnerabilities.

Can I use this for daily standups and sprint planning?▼

Yes, this supports Scrum Masters, product teams, and developers during daily standups, sprint planning, and retrospective reviews. It provides actionable visibility by surfacing risks and recommending next workflows from your sprint data.

What is the best way to automate scrum sprint reporting?▼

The best way to automate scrum sprint reporting is to parse your sprint-status.yaml file to classify stories and epics automatically. This reduces manual update toil by computing counts and producing a concise, prioritized next action.

How do I handle unrecognized statuses in sprint-status.yaml?▼

Handling unrecognized statuses in sprint-status.yaml is managed by ensuring only recognized statuses are accepted during processing. This validation prevents invalid story classifications from skewing your sprint risk indicators and computed counts.

Related Skills

Explore More Product & Management Skills→
deltatreedeltatree

bmad-sprint-status

Parse sprint-status.yaml to summarize status, identify risks, and recommend next actions.

Community
Advanced
devalexanderdazadevalexanderdaza

bmad-sprint-status

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

Community
Advanced
enigmaicon-engenigmaicon-eng
1

bmad-sprint-status

Summarize sprint progress from sprint-status.yaml and recommend the next workflow step.

Community
Intermediate
wahabmalikwahabmalik

bmad-sprint-planning

Parse epic files, detect story statuses, and generate a YAML sprint status file.

Community
Intermediate