bmad-sprint-planning

Parse epic files to generate a complete sprint-status.yaml.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow automates sprint planning by generating a complete sprint-status.yaml from epic files and planning artifacts, reducing manual tracking overhead.

Core Features & Use Cases

  • Derives epic and story statuses from epic files to create a coherent sprint plan
  • Preserves higher statuses when new information arrives to avoid regressions
  • Produces a ready-to-use sprint-status.yaml for multi-epic projects and iterative planning

Quick Start

Run sprint planning by reading all epic files and updating 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 plan from epic files?

To generate a sprint plan from epic files, the skill parses your epic documents to derive a complete sprint-status.yaml, mapping epics to stories and applying a consistent status workflow across the entire project.

How does epic-to-story mapping work in sprint planning?

Epic-to-story mapping works by parsing your epic files to extract story relationships, which are then reflected in a generated sprint-status.yaml file to maintain structural consistency across your project planning artifacts.

Can I update sprint-status.yaml without losing existing progress?

Yes, you can update sprint-status.yaml without losing existing progress because the workflow preserves higher statuses when applying new information, ensuring no regressions occur in your sprint tracking.

What is the best way to track agile workflow statuses across multiple epics?

The best way to track agile workflow statuses across multiple epics is to derive a machine-readable sprint-status.yaml file that automatically maps epics to stories and maintains status consistency for all entries.

Do I need specific project management tools to automate sprint planning with YAML?

No specific project management tools are required to automate sprint planning with YAML, as the workflow directly parses your existing epic files to produce a ready-to-use sprint-status.yaml for iterative planning.

Why does my sprint status update cause regressions in epic tracking?

Sprint status updates cause regressions when new information overwrites existing progress, but this skill prevents that by preserving higher statuses and maintaining consistency with existing entries in your sprint-status.yaml.