bmad-sprint-planning

Parse epic files to generate a deterministic sprint-status.yaml for project tracking.

Updated Sep 27, 2025
One-click install
npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-sprint-planning-cbanzaime23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/Cbanzaime23/Booking-System/tree/main/.agent/skills/bmad-sprint-planning
Command: npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-sprint-planning-cbanzaime23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint planning and progress tracking by converting epic and story data into a deterministic sprint-status.yaml that teams can monitor and update.

Core Features & Use Cases

  • Parse epic files to extract stories and statuses
  • Generate and maintain a structured sprint-status.yaml as a single source of truth
  • Use in engineering project planning, backlog grooming, and release alignment

Quick Start

Ask the sprint planning skill to generate a sprint-status.yaml from all epics and stories.

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 from epics and stories?

To generate a sprint-status.yaml, you parse epic files to extract story statuses and compile them into a deterministic YAML artifact for project tracking. This provides a single source of truth for sprint progress reporting.

What is the best way to track sprint progress from multiple epic files?

Tracking sprint progress from multiple epics is best handled by parsing local story files to detect statuses and writing them into a structured sprint-status.yaml. This enables automated progress reporting and release alignment across teams.

Does sprint planning work without external dependencies?

Sprint planning works without external dependencies, relying on local epic and story files to resolve workflow steps. It loads configuration and detects statuses locally to output a deterministic YAML artifact for monitoring.

Can I use a YAML artifact for backlog grooming and release alignment?

You can use a generated YAML artifact for backlog grooming and release alignment by consolidating epic and story data into a single source of truth. It allows teams to monitor updates and maintain structured sprint tracking.

Why does my sprint status reporting show inconsistent epic data?

Sprint status reporting shows inconsistent epic data when local story files are not parsed deterministically into a single YAML artifact. Generating a structured sprint-status.yaml resolves workflow steps and standardizes status detection across all epics.