bmad-sprint-status

Summarizes sprint-status.yaml into story counts, risks, and next workflow recommendations.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/unbakedcosmos/thumbnailer --skill bmad-sprint-status-unbakedcosmos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-sprint-status
Source: https://github.com/unbakedcosmos/thumbnailer/tree/main/.claude/skills/bmad-sprint-status
Command: npx skills add https://github.com/unbakedcosmos/thumbnailer --skill bmad-sprint-status-unbakedcosmos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agile teams lose track of where their sprint stands when status lives in a raw YAML file. This Skill parses sprint-status.yaml, aggregates story and epic counts, surfaces risks like stale data or orphaned stories, and recommends the next BMAD workflow action. ## Core Features & Use Cases - Sprint Summarization: Parses sprint-status.yaml to count stories and epics by status (backlog, ready-for-dev, in-progress, review, done) and lists open action items. - Risk Detection: Flags stale status files, orphaned stories, in-progress epics without stories, and unrecognized status values with interactive correction. - Next-Action Recommendation: Selects the next workflow (dev-story, code-review, create-story, or retrospective) based on priority rules, with interactive, data, and validate execution modes. - Use Case: A developer asks "check sprint status" and immediately sees that 3 stories are in review, the status file is 10 days old, and the recommended next step is running code-review on story 2-1. ## Quick Start Ask the assistant to check sprint status and show the current sprint summary with risks and the recommended next workflow.

Frequently Asked Questions about bmad-sprint-status

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

FAQPage Schema
How do I check sprint status in a BMAD project?▼

Ask the assistant to check or show sprint status. The Skill reads sprint-status.yaml from your implementation artifacts directory, counts stories and epics by status, lists open action items, and recommends the next workflow to run.

What is sprint-status.yaml and how is it created?▼

sprint-status.yaml is the tracking file containing generated and last_updated timestamps, project metadata, and a development_status map of epics and stories. It is created by running the sprint-planning workflow; if missing, this Skill directs you to run sprint-planning first.

What happens if sprint-status.yaml contains invalid status values?▼

The Skill validates all statuses against known values (backlog, ready-for-dev, in-progress, review, done for stories; backlog, in-progress, done for epics). In interactive mode it lists invalid entries and prompts you to correct them, writing fixes back to the file.

Can I use sprint status data in other workflows?▼

Yes. The Skill supports a data mode that returns structured outputs like next_workflow_id, next_story_id, status counts, open action items, and risks, plus a validate mode that checks file integrity and returns is_valid with error details.

Why does the sprint status report warn about stale data?▼

The Skill compares the last_updated timestamp (falling back to generated) against the current date. If the file is more than 7 days old, it warns that sprint-status.yaml may be stale so you know the summary may not reflect current work.