bmad-sprint-status

Parse YAML tracking files to summarize sprint status and identify project risks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the lack of visibility into sprint progress by automatically parsing status files, identifying potential bottlenecks, and recommending the next logical step in your development workflow.

Core Features & Use Cases

  • Automated Status Reporting: Aggregates story and epic statuses from your project configuration to provide an instant snapshot of sprint health.
  • Risk Detection: Proactively flags stale data, orphaned stories, and missing dependencies to keep your team on track.
  • Workflow Integration: Recommends specific follow-up actions like code reviews or story creation based on the current state of your sprint.

Quick Start

Ask the assistant to check sprint status to receive a summary of your current progress and the next recommended 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 an automated sprint status report from YAML tracking files?

Sprint risk detection works by parsing your project configuration to proactively flag stale data, orphaned stories, and missing dependencies. It identifies potential bottlenecks to help your software development team stay on track and maintain workflow integrity.

Can I use this to identify project risks and bottlenecks in an agile workflow?

Sprint risk detection works by parsing your project configuration to proactively flag stale data, orphaned stories, and missing dependencies. It identifies potential bottlenecks to help your software development team stay on track and maintain workflow integrity.

What is the best way to get actionable insights on epic and story progress?

You need project-specific YAML configuration files containing your story and epic tracking data. The Skill requires access to these files to parse statuses and follows defined status validation rules to ensure data integrity before generating sprint insights.

Do I need specific configuration files to check sprint health and visibility?

You need project-specific YAML configuration files containing your story and epic tracking data. The Skill requires access to these files to parse statuses and follows defined status validation rules to ensure data integrity before generating sprint insights.

How does workflow automation recommend the next logical step in a development lifecycle?

Workflow automation recommends the next logical step by evaluating your current sprint progress against defined rules. It suggests targeted follow-up actions like initiating code reviews or creating new stories to keep your development lifecycle moving efficiently.