bmad-sprint-planning

Parse epic files and generate a structured sprint-status.yaml.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Wizarck/iguanatrader --skill bmad-sprint-planning-wizarck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/Wizarck/iguanatrader/tree/main/skills/bmad-sprint-planning
Command: npx skills add https://github.com/Wizarck/iguanatrader --skill bmad-sprint-planning-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizes and tracks sprint work by converting epic files into a structured sprint-status.yaml, reducing manual coordination and oversight.

Core Features & Use Cases

  • Automatically discover epics and stories from epic-*.md files and optional index structures.
  • Generate a complete sprint-status.yaml that lists epics, stories, and retrospectives in the correct order with statuses.
  • Validate consistency between epic content and the generated status file, preserving existing statuses and preventing downgrades.

Quick Start

Run sprint planning on your epics repository to generate the sprint-status.yaml.

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 epic files?

You can generate a sprint-status.yaml by running sprint planning on your repository to parse epic-*.md files, extract work items, and build a structured status file that preserves existing statuses and prevents downgrades.

How does sprint planning handle monorepos with sharded epic structures?

Sprint planning handles monorepos with sharded epic structures by reading multiple epic-*.md files and any index when present, extracting all work items to build a complete sprint-status.yaml.

Do I need a specific project root to parse epics into a sprint plan?

Yes, parsing epics into a sprint plan requires a project root containing the _bmad/bmm/config.yaml file along with the epics/stories inputs to successfully generate the structured YAML status output.

What is the best way to track sprint work from epics in a YAML file?

The best way to track sprint work from epics in a YAML file is to automatically parse epic files and extract work items to build a complete sprint-status.yaml, reducing manual coordination and oversight.

Will generating a new sprint-status.yaml overwrite my existing story statuses?

Generating a new sprint-status.yaml will not overwrite your existing story statuses; the process validates consistency between epic content and the generated status file while preserving existing statuses and preventing downgrades.