skills.rest
Rinzler78
Rinzler78COMMUNITY
Explore all skills by this author →
GitHub

bmad-sprint-status

Summarize sprint progress and recommend next workflow actions from sprint-status.yaml data.

1|Updated Dec 22, 2022
Search Tags:#workflow#agile#project tracking#status reporting#sprint status#risk detection
One-click install
npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-sprint-status-rinzler78
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-sprint-status
Source: https://github.com/Rinzler78/osmosis-launcher/tree/main/.agents/skills/bmad-sprint-status
Command: npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-sprint-status-rinzler78

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly understand current sprint progress, identify delivery risks, and choose the most appropriate next workflow step without manually inspecting status files.

Core Features & Use Cases

  • Sprint Reporting: Summarize story and epic counts by status so teams can see work distribution at a glance.
  • Risk Surfacing: Detect stale updates, review bottlenecks, orphaned stories, and epics that are blocked by missing work.
  • Next-Step Recommendation: Suggest the most relevant follow-up workflow such as development, code review, story creation, or retrospectives.
  • Use Case: A scrum lead asks for a sprint checkpoint and gets a concise status summary plus the best next action for the team.

Quick Start

Ask the skill to check sprint status for the current project and recommend the next workflow action.

Frequently Asked Questions about bmad-sprint-status

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

FAQPage Schema
How do I generate a sprint status report from a yaml file?▼

Generating a sprint status report requires parsing a sprint-status.yaml file to summarize story and epic counts by status, surface delivery risks, and recommend the best next workflow action for the team.

What is the best way to identify delivery risks in agile project tracking?▼

Identifying delivery risks in agile project tracking involves analyzing sprint status data to detect stale updates, review bottlenecks, orphaned stories, and epics blocked by missing work.

How do I recommend the next workflow action for a sprint checkpoint?▼

Recommending the next workflow action for a sprint checkpoint involves validating current workflow states and suggesting relevant follow-up steps like development, code review, story creation, or retrospectives.

Can I use sprint status data to surface review bottlenecks and orphaned stories?▼

Yes, you can use sprint status data to surface review bottlenecks and orphaned stories by parsing sprint-status.yaml files to detect stale updates and identify epics blocked by missing work.

Do I need a sprint-status.yaml file to track sprint progress and work distribution?▼

Yes, you need a sprint-status.yaml file to track sprint progress and work distribution, because the skill parses this specific file format to validate workflow states and summarize story and epic counts by status.

Related Skills

Explore More Software Engineering Skills→
imonmiimonmi

bmad-sprint-status

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

Community
Advanced
ImaginerLabsImaginerLabs

bmad-sprint-status

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

Official
Advanced
lorenzogmlorenzogm
15

bmad-sprint-planning

Generate sprint status files from epic files with Python scripts.

Community
Intermediate
DavidsonGomesDavidsonGomes

evo-sprint-status

Summarize current sprint status and surface blockers and risks.

Community
Advanced