bmad-sprint-status

Summarize sprint status and surface risks across Epics and Stories.

Updated Nov 6, 2025
One-click install
npx skills add https://github.com/skyoxu/godotgame --skill bmad-sprint-status-skyoxu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-status
Source: https://github.com/skyoxu/godotgame/tree/main/.agents/skills/bmad-sprint-status
Command: npx skills add https://github.com/skyoxu/godotgame --skill bmad-sprint-status-skyoxu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint teams often struggle to get a concise, actionable view of progress and risks across Epics and Stories. This skill gathers status data, surfaces blockers, and clarifies next steps.

Core Features & Use Cases

  • Summarizes sprint status across Epics and Stories
  • Detects risks like stalled work, outdated statuses, and orphaned items
  • Recommends next actions and workflows for sprint planning

Quick Start

Run the sprint-status workflow to generate a concise status summary and recommended next actions for the current sprint.

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 summary of sprint status across Epics and Stories?

To get a sprint status summary, run the sprint-status workflow to aggregate progress data across Epics and Stories, validate known status values, and surface blockers for your active development team.

What is the best way to detect stalled work and outdated sprint data?

Detecting stalled work and outdated sprint data is handled by validating known status values and identifying stale sprint-data, which surfaces orphaned items and blockers across your active Epics and Stories.

How does sprint risk detection guide team planning?

Sprint risk detection guides team planning by surfacing blockers, stalled work, and orphaned items, then recommending the next workflow action to clarify steps for sprint planning and retrospectives.

Can I use this sprint status workflow for active development team retrospectives?

Yes, you can use this sprint status workflow for active development team retrospectives, as it provides visibility into Epics and Stories to guide planning and recommend next workflow actions.

What should I do when sprint-data is stale and not reflecting current progress?

When sprint-data is stale, the workflow detects outdated statuses and stalled work, then recommends the next workflow action to update your sprint planning and restore accurate visibility into Epics.