bmad-sprint-planning

Parse epic markdown files and generate a validated sprint-status.yaml.

Updated May 17, 2026
One-click install
npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill bmad-sprint-planning-thuantan2060
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/thuantan2060/facebook-sale-tracking/tree/main/.agents/skills/bmad-sprint-planning
Command: npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill bmad-sprint-planning-thuantan2060

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

It turns scattered epic and story documents into a single, consistently structured sprint-status.yaml, so teams can track readiness and progress without manual bookkeeping.

Core Features & Use Cases

  • Epic & story inventory generation: Scans epic markdown files, extracts epic/story identifiers and titles, and creates a complete set of tracking keys.
  • Intelligent status detection: Determines each story’s status by checking whether story files exist and preserves any already-advanced statuses in sprint-status.yaml.
  • Ordered sprint tracking output: Writes an end-to-end YAML file containing epic, stories, and retrospective entries in the expected sequence for validation and ongoing updates.

Quick Start

Ask the AI to run sprint planning to generate or refresh sprint-status.yaml based on your current 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 epic markdown files?

To generate sprint-status.yaml from epic markdown files, the Skill parses your planning artifacts to extract epic and story identifiers, automatically creating a structured tracking file with correct status state-machine defaults.

Can I preserve existing story statuses when regenerating sprint tracking YAML?

Yes, you can preserve existing story statuses during sprint tracking YAML regeneration. The Skill detects whether story files exist and intelligently retains any already-advanced statuses found in the existing sprint-status.yaml.

What is the best way to automate epic and story inventory generation for project planning?

Automating epic and story inventory generation is best handled by scanning epic markdown files to extract identifiers and titles, producing a consistently structured YAML output that eliminates manual bookkeeping for sprint planning.

Does bmad-sprint-planning work with sharded epic indexes?

Yes, bmad-sprint-planning works with sharded epic indexes. It applies full-epic loading and sharded index parsing to extract all epics and stories, ensuring complete sprint status tracking from complex planning artifacts.

How to track sprint readiness and progress without manual bookkeeping?

Tracking sprint readiness without manual bookkeeping involves turning scattered epic and story documents into a single, consistently structured sprint-status.yaml file containing ordered epic, story, and retrospective entries for ongoing validation and updates.

What happens to custom workflow statuses when refreshing sprint-status.yaml?

When refreshing sprint-status.yaml, custom workflow statuses are preserved. The Skill resolves workflow customization and maintains any advanced existing statuses while applying correct status state-machine defaults to new entries.