bmad-sprint-planning

Parse epic Markdown files and generate a deterministic sprint-status.yaml.

Updated Nov 6, 2025
One-click install
npx skills add https://github.com/skyoxu/godotgame --skill bmad-sprint-planning-skyoxu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/skyoxu/godotgame/tree/main/.agents/skills/bmad-sprint-planning
Command: npx skills add https://github.com/skyoxu/godotgame --skill bmad-sprint-planning-skyoxu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert epic definitions into actionable sprint status by parsing epic Markdown files and generating a single sprint-status.yaml that reflects current work items.

Core Features & Use Cases

  • Parse epic files to extract epics and stories and build a complete inventory
  • Detect current statuses by comparing epic content with existing stories and status metadata
  • Generate, validate, and export a deterministic sprint-status.yaml mapped to the project workflow
  • Use case: a PM feeds updated epics.md and the skill outputs a ready-to-use sprint-status.yaml for project tracking

Quick Start

Parse your epic files and generate the sprint-status.yaml to track sprint progress.

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

Sprint status automation parses epic Markdown files to extract epics and stories, detects current statuses by checking the local stories directory, and exports a deterministic sprint-status.yaml document mapping items to workflow stages.

What is the state machine for story and epic statuses in sprint tracking?

The sprint tracking state machine enforces epic transitions from backlog to in-progress to done, while stories move sequentially from backlog to ready-for-dev, in-progress, review, and done, ensuring valid workflow progression in the generated YAML.

How does sprint planning automation detect existing story statuses?

Sprint planning automation detects story statuses by comparing epic Markdown content with existing files in the local stories directory, preserving higher statuses to maintain accurate project tracking without overwriting completed work.

Does sprint-status.yaml generation work without external project management dependencies?

Yes, sprint-status.yaml generation works without external project management dependencies, relying solely on local epic Markdown files and a stories directory to produce a structured YAML file for sprint tracking.

Why does my sprint-status.yaml preserve a higher status instead of overwriting it?

Your sprint-status.yaml preserves higher statuses to enforce the status state machine deterministically, ensuring that detected regressions in local story files do not accidentally overwrite completed work during the sprint tracking update.