bmad-sprint-planning

Parse epic markdown files and generate sprint status entries in sprint-status.yaml.

36|16|Updated May 1, 2026
One-click install
npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-sprint-planning-tronghieu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/tronghieu/lumina-wiki/tree/main/.agents/skills/bmad-sprint-planning
Command: npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-sprint-planning-tronghieu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns scattered epic and story files into a single, consistent sprint status tracker, so teams can see readiness and progress without manually updating a spreadsheet.

Core Features & Use Cases

  • Epic-to-status generation: Creates epic, story, and retrospective status entries with predictable keys and default states.
  • Intelligent status detection: Infers story statuses by checking whether corresponding story markdown files already exist, and preserves any more advanced statuses already present in the sprint-status.yaml.
  • Validation and reporting: Verifies coverage (no missing or extra items), confirms legal status values, ensures valid YAML, and outputs a completion summary.

Quick Start

Ask your agent to run the sprint planning workflow by saying: "run sprint planning".

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 sprint status from epic markdown files?

Sprint status generation parses epic markdown files and produces a complete development_status section in sprint-status.yaml. It infers story statuses by checking for corresponding story files and preserves any more advanced statuses already present in the YAML.

How does story readiness detection work for sprint planning?

Story readiness detection works by checking the filesystem for the existence of per-story markdown files. It infers default statuses based on file presence while preserving any existing more advanced statuses in sprint-status.yaml without downgrading them.

Can I use YAML validation to prevent missing or extra items in my sprint tracker?

YAML validation verifies coverage by confirming no missing or extra items exist in your sprint tracker. It validates legal status values, ensures valid YAML syntax, and outputs a completion summary for your sprint planning workflow.

Do I need specific config settings to customize sprint status output language?

Config-driven language and output settings are resolved during sprint status generation to customize the output. The workflow applies customization resolution to ensure the generated sprint-status.yaml meets your specific language and formatting requirements.

What is the best way to track epic and story progress without manual spreadsheet updates?

Generating a sprint-status.yaml file from scattered epic and story files tracks progress automatically. This approach creates consistent epic, story, and retrospective status entries with predictable keys and default states, eliminating manual spreadsheet maintenance.