bmad-sprint-status

Summarize sprint status and recommend the next BMad workflow action.

Updated May 23, 2026
One-click install
npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-sprint-status-diegosanchespereira1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-status
Source: https://github.com/diegosanchespereira1/lavarapido/tree/main/lava-rapido/.agents/skills/bmad-sprint-status
Command: npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-sprint-status-diegosanchespereira1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual work of checking sprint progress, spotting blockers, and deciding what the team should do next.

Core Features & Use Cases

  • Sprint Snapshot: Summarizes story, epic, and retrospective status from the sprint status file.
  • Risk Detection: Flags stale status data, orphaned stories, missing story coverage, and review-stage work that needs attention.
  • Next Workflow Recommendation: Points to the most relevant next BMad workflow, such as development, code review, story creation, or retrospective handling.
  • Use Case: A developer asks for the current sprint state before standup and quickly gets counts, risks, and the next action to take.

Quick Start

Use the bmad-sprint-status skill to summarize the current sprint, surface risks, and recommend the next workflow from the sprint status file.

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 next workflow actions?

To summarize sprint status and identify next workflow actions, you can parse sprint metadata files to generate counts of stories and epics, detect risks like stale files or orphaned stories, and recommend the next development step. This applies to BMad-managed sprint planning.

What is the best way to track developer progress and spot blockers in a sprint?

Tracking developer progress and spotting blockers is done by validating sprint metadata to detect risks such as missing story coverage, stale status data, and review-stage work needing attention. This surfaces the current state and flags issues before standup.

How does risk detection work for orphaned stories and stale files?

Risk detection for orphaned stories and stale files works by validating recognized status values within sprint metadata files. It identifies stories lacking epic coverage, flags outdated status data, and highlights review-stage work that requires immediate attention.

Can I use sprint metadata to check retrospective readiness across epics?

Yes, you can use sprint metadata to check retrospective readiness across epics. The process summarizes epic, story, and retrospective status from the sprint status file to determine if the team is ready for review and recommends the appropriate retrospective handling workflow.

Do I need a specific file format to generate a sprint snapshot?

Yes, you need a validated sprint-status.yaml file to generate a sprint snapshot. The system requires this specific sprint metadata format containing recognized status values to accurately summarize progress and recommend the next workflow action.