skills.rest
ldk-hub
ldk-hubCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bmad-sprint-status

Summarize sprint status and surface risks from sprint-status.yaml.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Summarize sprint status and surface risks from sprint-status.yaml, delivering visibility into blockers and progress for agile teams.

Core Features & Use Cases

  • Analyze sprint-status.yaml to count and categorize stories and epics (backlog, in-progress, ready-for-dev, review, done) and retrospectives; surface orphaned items and stale data.
  • Detect risks and propose next actions, such as triggering dev-workflows or planning steps, and provide a concise recommended path.
  • Leverage configured overrides and project context to tailor guidance and ensure traceability.

Quick Start

Activate the sprint-status skill and run the sprint-status workflow to generate a concise status summary and actionable next steps.

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 a YAML file?▼

To summarize sprint status and surface risks, the Skill analyzes the sprint-status.yaml file to count stories and epics by category, identify blockers, and compute recommended next actions for agile teams.

What is the best way to track agile blockers and epic progress?▼

Tracking agile blockers and epic progress is achieved by validating statuses against known values and categorizing stories into backlog, in-progress, ready-for-dev, review, and done states to provide clear visibility.

How do I detect orphaned items and stale data in my sprint workflow?▼

Detecting orphaned items and stale data in your sprint workflow involves analyzing sprint-status.yaml to categorize retrospectives and surface items that lack proper progress tracking or current updates.

Can I use configured overrides to tailor sprint planning guidance?▼

You can use configured overrides and project context to tailor sprint planning guidance, ensuring traceability and providing a concise recommended path for triggering dev-workflows or planning steps.

How does the sprint risk analysis select the next workflow to execute?▼

Sprint risk analysis selects the next workflow to execute by detecting risks within the sprint-status.yaml file, proposing targeted next actions, and computing the recommended path for the agile team.

Does sprint status tracking work without external dependencies?▼

Sprint status tracking works without external dependencies, utilizing an advanced internal design to validate statuses, compute category counts, and surface blockers directly from the sprint-status.yaml file.

Related Skills

Explore More Software Engineering Skills→
imonmiimonmi

bmad-sprint-status

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

Community
Advanced
mschuerigmschuerig

bmad-sprint-status

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

Community
Intermediate
0xMerl990xMerl99
1

project-manager

Guide Agile sprint planning, estimation, and risk management for software teams.

Community
Intermediate
johnatas-henriquejohnatas-henrique

sprint-status

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

Community
Intermediate