bmad-sprint-planning

Consolidate epics and stories into a sprint-status.yaml with status rules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the generation of sprint status tracking by converting epic and story definitions into a single, auditable sprint-status.yaml, eliminating manual consolidation and drift between planning and execution.

Core Features & Use Cases

  • Generate a complete sprint-status.yaml by scanning epic files and applying status rules.
  • Preserve existing statuses to avoid regressions, upgrading only when new work items appear.
  • Suitable for Scrum Masters, product managers, and engineering leads who need a clear artifact for sprint planning and progress tracking.

Quick Start

Run the sprint planning workflow to generate sprint-status.yaml from all 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 a sprint-status.yaml from existing agile epic files?

To generate a sprint-status.yaml, the skill scans your planning artifacts and consolidates defined epics and stories into a single, auditable YAML file that serves as a source of truth for sprint tracking.

What is the best way to track agile sprint progress without manual status consolidation?

Tracking sprint progress without manual consolidation is achieved by applying status rules to generate an ordered sprint-status.yaml, automatically reflecting current progress while preserving previously set states to avoid regressions.

Can I preserve existing sprint statuses when adding new stories to the sprint plan?

Yes, you can preserve existing sprint statuses. The skill upgrades statuses only when new work items appear, ensuring your agile sprint plan retains previously set states and prevents tracking regressions.

Does this sprint planning approach work for teams coordinating epics across multiple sprints?

Yes, this sprint planning approach is designed for agile teams coordinating epics and stories across multiple sprints to maintain a single source of sprint truth in a structured YAML schema.

Why does my sprint-status.yaml need to adhere to a specific schema?

Your sprint-status.yaml needs to adhere to a defined schema to ensure reliable tracking and provide ordered epic, story, and retrospective entries, eliminating drift between planning and execution.