bmad-sprint-planning

Parse epic markdown files into a normalized sprint-status.yaml inventory.

Updated May 23, 2026

Search Tags:#workflow automation #sprint planning #markdown parsing #epic tracking #yaml generation #story status

Ready to run

npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-sprint-planning-diegosanchespereira1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/diegosanchespereira1/lavarapido/tree/main/lava-rapido/.agents/skills/bmad-sprint-planning
Command: npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-sprint-planning-diegosanchespereira1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint planning status drift makes it hard to know which epics and stories exist, what is ready, and what progress has been preserved across updates.

Core Features & Use Cases

Epic Parsing: Reads one or many epic markdown files and extracts every epic, story, and retrospective entry into a complete tracking inventory.

Status Generation: Builds a normalized sprint-status.yaml file with default states, preserves more advanced existing statuses, and enforces valid workflow transitions.

Use Case: Use this Skill when a team needs a reliable, repeatable way to turn planning documents into an up-to-date sprint tracking file.

Quick Start

Use the bmad-sprint-planning skill to scan the repository epics and generate an accurate sprint-status.yaml file.

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 tracking from epic markdown files?▼

To generate sprint status tracking from epic markdown files, you parse all epics, stories, and retrospectives. This process extracts the planning entries and builds a complete, normalized YAML inventory for progress tracking.

What is the best way to maintain consistent story status across multiple development epics?▼

The best way to maintain consistent story status is to use deterministic YAML generation. This approach normalizes story keys and enforces valid workflow transitions, ensuring reliable file-system-based progress tracking across all epics.

Does sprint planning YAML generation preserve existing story statuses?▼

Yes, sprint planning YAML generation preserves existing story statuses. The parsing mechanism applies default states to new entries while specifically preserving more advanced existing statuses during the inventory build.

Can I use markdown parsing for sprint planning in repositories with multiple retrospective entries?▼

Yes, you can use markdown parsing for sprint planning in repositories with multiple retrospective entries. The parser reads one or many epic files and extracts every epic, story, and retrospective entry into a complete tracking inventory.

Why does legal state validation matter when generating a sprint-status.yaml file?▼

Legal state validation matters when generating a sprint-status.yaml file because it enforces valid workflow transitions. This prevents invalid status updates and ensures deterministic, consistent progress tracking across the repository.