bmad-sprint-planning

Parse epic markdown files and generate sprint-status.yaml inventory.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/cassioalexandre/agf --skill bmad-sprint-planning-cassioalexandre
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/cassioalexandre/agf/tree/main/_bmad/bmm/4-implementation/bmad-sprint-planning
Command: npx skills add https://github.com/cassioalexandre/agf --skill bmad-sprint-planning-cassioalexandre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint planning becomes slow and error-prone when sprint status must be manually synced with ever-changing epic and story documents.

Core Features & Use Cases

  • Sprint status generation: Produces a complete sprint-status.yaml by parsing epic and story files.
  • Status detection and consistency checks: Detects story presence via the stories folder and preserves already-advanced statuses to avoid downgrades.
  • Ordered workflow output: Ensures entries are emitted in a predictable order (epic, its stories, its retrospective, then the next epic) suitable for continuous governance.

Quick Start

Ask the AI agent to run sprint planning and generate the sprint-status.yaml from your epic files.

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, the Skill parses epic markdown files and builds a complete sprint-status.yaml inventory. It detects current story states via the stories directory and outputs YAML ordered by epic, stories, and retrospectives.

How does sprint-status.yaml generation handle existing story files?

Sprint-status.yaml generation detects story presence via the stories folder and preserves already-advanced statuses to avoid downgrades. This ensures existing progress in your agile governance workflow is maintained without manual re-entry.

Do I need a project config file for sprint planning automation?

Yes, sprint planning automation requires loading project configuration from _bmad/bmm/config.yaml. This config file provides the necessary environment context to parse epics and generate the sprint-status.yaml inventory correctly.

What is the best way to maintain agile governance documentation for sprints?

The best way to maintain agile governance documentation is auto-generating an ordered sprint-status.yaml file. This ensures entries are emitted predictably by epic, its stories, and its retrospective, providing continuous governance tracking.

Can sprint planning YAML output be generated if story files do not exist yet?

Yes, sprint planning YAML output can be generated when story files may or may not already exist. The Skill detects story presence via the stories directory and builds the sprint-status.yaml inventory accordingly.