bmad-sprint-planning

Convert epic and story details into a structured sprint-status.yaml.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Yukine5377/common --skill bmad-sprint-planning-yukine5377
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/Yukine5377/common/tree/main/.cursor/skills/bmad-sprint-planning
Command: npx skills add https://github.com/Yukine5377/common --skill bmad-sprint-planning-yukine5377

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint planning often struggles to translate scattered epic details into a unified, actionable track. This skill generates a comprehensive sprint-status file from epics and stories, ensuring visibility and alignment across teams.

Core Features & Use Cases

  • Convert epic definitions into a structured sprint-status.yaml with automatic status detection.
  • Preserve higher statuses and ensure YAML validity while updating progress as work advances.
  • Use cases include planning iterations, tracking progress across multiple epics, and generating reports for stakeholders.

Quick Start

Ask it to generate a sprint-status.yaml from your epics to start tracking 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 automatically generate a sprint status YAML from multiple epics?▼

Sprint status YAML files provide a structured, machine-readable format for tracking iteration progress. They enable automatic status detection across multiple epics and ensure visibility and alignment across product development teams.

How does auto-detection work when updating sprint status from existing epic files?▼

Auto-detection scans existing epic files to identify current work progress and maps it to defined statuses. It then updates the sprint-status.yaml while applying safeguards to preserve higher statuses and maintain valid YAML structure.

Can I use this sprint planning automation for tracking progress across multiple epics in product development?▼

Yes, this automation suits product development workflows managing multiple epics across iterations. It generates a comprehensive sprint-status file from epics and stories, enabling progress tracking and stakeholder report generation.

What safeguards prevent data loss when updating sprint status YAML?▼

The system applies safeguards to preserve higher statuses and ensure valid YAML generation when updating progress. This prevents status regression and maintains file integrity as work advances across iterations.

Do I need predefined status definitions to convert epics into a sprint-status.yaml?▼

Yes, status definitions are required to categorize epic and story progress accurately during auto-detection. These definitions are applied when converting epic details into a structured and valid sprint-status.yaml file.