bmad-sprint-planning

Generate sprint-status.yaml files from epic documents and story inventories.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-sprint-planning-geneducation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/bmad-sprint-planning
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-sprint-planning-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of turning epic documents into a complete sprint status tracker, making it easy to see what work exists, what is ready, and what is already done.

Core Features & Use Cases

  • Epic and story discovery: Finds all epics and stories from whole or sharded planning documents.
  • Status file generation: Builds a complete sprint-status.yaml structure in the required order.
  • Progress preservation and validation: Detects existing story files, avoids downgrading status, and checks coverage against the epic source files.
  • Use case: Use it when a team needs a reliable sprint planning snapshot that stays aligned with repository-based epic documentation.

Quick Start

Ask me to run sprint planning for this repository so I can generate or update the sprint status file from the available epic documents.

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 documents?

To generate sprint status tracking from epic documents, you need a tool that parses file-based planning artifacts and outputs a structured sprint-status YAML file. This process discovers stories from sharded or whole epics and validates their current progress.

What is the best way to track sprint planning using YAML files?

Tracking sprint planning with YAML files involves creating a structured status tracker that preserves story ordering. You can generate a sprint-status.yaml file from your epic markdown inventories to maintain a reliable snapshot of what work is ready and what is done.

How does story status validation work with file-based epic planning?

Story status validation works by detecting existing story files and checking their coverage against epic source files. This ensures that previously detected progress is never downgraded during the sprint-status YAML generation process.

Can I use sharded markdown files for sprint planning and story tracking?

Yes, you can use sharded markdown files for sprint planning and story tracking. The discovery process supports both whole and sharded epic planning documents to build a complete sprint-status YAML structure without losing existing progress.

Why does my sprint status tracker downgrade existing story progress?

Sprint status tracking should never downgrade previously detected progress. If your workflow automation downgrades status, it lacks proper validation against existing story files; a correct generator preserves prior states while updating the YAML output.