bmad-sprint-planning

Name: bmad-sprint-planning
Availability: InStock
Author: ImaginerLabs

Generate sprint-status.yaml from epic and story markdown files.

Updated Apr 10, 2026

Search Tags:#automation #workflow #epics #yaml #sprint-planning #story-tracking #sprint-status

Ready to run

npx skills add https://github.com/ImaginerLabs/skill-manager --skill bmad-sprint-planning-imaginerlabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/ImaginerLabs/skill-manager/tree/main/.trae/skills/bmad-sprint-planning
Command: npx skills add https://github.com/ImaginerLabs/skill-manager --skill bmad-sprint-planning-imaginerlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating and maintaining an accurate sprint-status.yaml from scattered epic and story markdown files is time-consuming and error-prone; this Skill automates discovery, status inference, and validation so teams can reliably track sprint progress without manual reconciliation.

Core Features & Use Cases

Epic and Story Discovery: Scans project planning artifacts for whole or sharded epic files and builds a complete inventory of epics and stories.
Status Inference and Preservation: Detects story artifact files to upgrade statuses, preserves any existing advanced statuses in sprint-status.yaml, and enforces a defined status state machine.
Validation and Output: Generates or updates an ordered sprint-status.yaml, performs coverage and YAML validation checks, and reports summary metrics for planning reviews.

Quick Start

Run the sprint planning workflow to scan your project's epic files and generate or update sprint-status.yaml with detected stories and inferred statuses.

Frequently Asked Questions about bmad-sprint-planning

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

FAQPage Schema

How do I generate a sprint-status.yaml file from epic and story markdown files?▼

The sprint planning workflow automates sprint-status.yaml generation by scanning project directories for epic and story markdown files, parsing headers and sections to extract epics and stories, and outputting an ordered YAML tracking file with inferred statuses.

How does status inference work for story tracking in sprint planning?▼

Status inference works by detecting existing story artifact files in the project directory to upgrade story statuses. The workflow preserves advanced statuses found in an existing sprint-status.yaml and validates all transitions against a defined state machine.

Can I use sprint planning automation with sharded epic files spread across multiple directories?▼

Yes, sprint planning automation works with sharded epic files. The workflow scans project planning artifacts for both whole and sharded epic files, building a complete inventory of epics and stories regardless of file distribution across the repository.

What is the best way to maintain sprint progress tracking without manual reconciliation of markdown files?▼

The best way to maintain sprint progress tracking without manual reconciliation is to run an automated sprint planning workflow that discovers epics and stories from markdown files, infers statuses from artifacts, validates YAML output, and reports summary metrics for planning reviews.

Does the sprint-status.yaml generation validate coverage and YAML format?▼

Yes, sprint-status.yaml generation performs both coverage and YAML validation checks. The workflow validates the output against a defined state machine, ensuring all stories are accounted for and the YAML structure is correct before reporting summary metrics for planning reviews.

What happens to advanced statuses already in my sprint-status.yaml when I regenerate it?▼

When you regenerate sprint-status.yaml, the workflow preserves any existing advanced statuses found in the current file. It detects story artifact files to upgrade statuses while ensuring previously set advanced statuses are retained during the automated update.