skills.rest
deltatree
deltatreeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bmad-sprint-status

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a clear, concise summary of the current sprint status, highlighting potential risks and guiding the team on the next immediate action.

Core Features & Use Cases

  • Status Aggregation: Consolidates information from sprint-status.yaml to show counts of stories and epics by their current status (e.g., backlog, in-progress, done).
  • Risk Identification: Automatically detects common sprint risks such as stale status files, orphaned stories, or in-progress epics without associated stories.
  • Action Recommendation: Suggests the most appropriate next workflow or action based on the current sprint progress.
  • Use Case: A Scrum Master can use this skill at the start of a daily stand-up to quickly get an overview of the sprint's health, identify blockers, and decide on the team's focus for the day.

Quick Start

Check the current sprint status and identify any risks.

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 identify risks from a yaml file?▼

To summarize sprint status, you can parse a sprint-status.yaml file to aggregate story and epic counts, detect risks like orphaned stories, and recommend the next workflow action.

What sprint risks should I look for during agile status aggregation?▼

During agile sprint status aggregation, common risks include stale status files, orphaned stories lacking parent epics, and in-progress epics without any associated stories.

How does an automated workflow recommend the next scrum action based on sprint progress?▼

Automated workflow action recommendation validates story, epic, and retrospective statuses from your sprint-status.yaml file, then prioritizes subsequent actions like developing a story or reviewing code.

Can I use a yaml file to track agile stories and epics for daily stand-ups?▼

Yes, you can use a sprint-status.yaml file to track agile stories and epics, allowing a Scrum Master to quickly get an overview of sprint health and blockers for daily stand-ups.

What is the best way to validate sprint status categories before a scrum review?▼

The best way to validate sprint status categories is to parse your sprint-status.yaml file, ensuring stories and epics are grouped correctly into backlog, in-progress, and done states before action recommendation.

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
WizarckWizarck

bmad-sprint-status

Validate sprint-status.yaml data and detect risks for agile workflows.

Community
Advanced
imonmiimonmi

bmad-sprint-status

Summarizes sprint progress and risks from sprint-status.yaml files.

Community
Advanced
staticWagomUstaticWagomU
6

scrum-dashboard

Maintains a Scrum dashboard model in scrum.ts for backlog, sprint status, and progress tracking.

Community
Advanced