bmad-sprint-status

Parse sprint-status.yaml files to summarize sprint status and surface project risks.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-sprint-status-marcmontecalvo
Or copy as Structured Prompt for Agentâ–¼
Please help me install this Agent Skill.
Skill: bmad-sprint-status
Source: https://github.com/marcmontecalvo/kinward/tree/main/.agents/skills/bmad-sprint-status
Command: npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-sprint-status-marcmontecalvo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates the manual effort required to track sprint progress, identify bottlenecks, and maintain alignment across development teams by providing an automated, status-aware summary of project health.

Core Features & Use Cases

  • Automated Sprint Summarization: Parses sprint-status.yaml to provide a high-level overview of epics, stories, and action items.
  • Risk Detection: Automatically flags stale data, orphaned stories, and missing epic associations to ensure data integrity.
  • Actionable Recommendations: Suggests the next logical workflow step based on current sprint status, such as initiating code reviews or starting new development tasks.

Quick Start

Ask the assistant to check the current sprint status to receive a summary of progress and recommended next steps.

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 an automated sprint summary from YAML configuration files?â–¼

Automated sprint summarization parses your sprint-status.yaml to provide a high-level overview of epics, stories, and action items. It eliminates manual tracking effort by surfacing project health and progress directly from your structured configuration data.

What is the best way to detect orphaned stories and stale data in an agile workflow?â–¼

Detecting orphaned stories and stale data requires risk detection logic that flags missing epic associations and outdated entries to ensure data integrity. This automated validation surfaces project risks and bottlenecks without requiring manual cross-referencing of your sprint backlog.

How do I track epic and story progress within the BMad workflow engine?â–¼

Tracking epic and story progress operates within software development lifecycles by parsing structured YAML files integrated with the BMad workflow engine. It summarizes sprint status automatically and recommends follow-up actions based on the current development state.

Does sprint status tracking work without external project management dependencies?â–¼

Sprint status tracking works without external dependencies by relying entirely on project-specific sprint-status.yaml files. You only need structured YAML configuration data and BMad workflow engine integration to generate automated summaries and risk assessments.

Can I get actionable recommendations for the next logical workflow step in my sprint?â–¼

Actionable recommendations suggest the next logical workflow step based on current sprint status, such as initiating code reviews or starting new development tasks. The skill analyzes parsed YAML data to recommend targeted follow-up actions for your development team.

Why does my sprint summarization show missing epic associations and data integrity risks?â–¼

Sprint summarization shows missing epic associations because the risk detection mechanism automatically flags orphaned stories and stale data. These warnings ensure data integrity by highlighting structural gaps in your sprint-status.yaml configuration that require manual correction.