bmad-sprint-planning

Generate sprint-status.yaml from markdown epic and story files.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ncptuan/stock_backtest_project --skill bmad-sprint-planning-ncptuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/ncptuan/stock_backtest_project/tree/main/.claude/skills/bmad-sprint-planning
Command: npx skills add https://github.com/ncptuan/stock_backtest_project --skill bmad-sprint-planning-ncptuan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of turning epic documents into a usable sprint tracking file. It helps teams create a complete sprint-status.yaml that reflects every epic, every story, and each retrospective entry in a consistent order.

Core Features & Use Cases

  • Epic and story inventory generation: Scans planning documents to extract all epics and stories, then converts them into structured status keys.
  • Status bootstrap and preservation: Detects whether story files already exist to mark items as ready-for-dev, while preserving more advanced statuses from an existing tracking file.
  • Validation for completeness: Checks that no epics or stories are missing, no unexpected items are added, and all entries follow the expected workflow states.
  • Use case: A product or engineering team with epic markdown files can use this Skill to generate or refresh a sprint tracking file before planning, execution, or status review.

Quick Start

Run sprint planning to generate or refresh sprint-status.yaml from the 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 tracking file from epic markdown documents?

To generate a sprint status tracking file, this Skill parses markdown epic and story planning documents, converts story headings into kebab-case status keys, and outputs a complete sprint-status.yaml reflecting every epic and story in a consistent order.

What is the best way to automate backlog management for file-based story tracking?

Automating backlog management involves scanning planning directories to extract epics and stories, detecting existing story files to bootstrap ready-for-dev statuses, and validating YAML completeness to ensure no items are missing during sprint planning.

Can I preserve advanced workflow statuses when refreshing sprint-status.yaml?

Refreshing sprint-status.yaml preserves advanced statuses from an existing tracking file while bootstrapping new story items as ready-for-dev, ensuring no prior progress tracking is lost during backlog updates.

How does epic and story validation work for YAML completeness?

YAML completeness validation checks that no epics or stories are missing from the planning documents, no unexpected items are added, and all generated entries follow the expected sprint planning workflow states.

Do I need sharded epic documents to run sprint planning, or are whole documents supported?

Sprint planning supports both whole and sharded epic documents, parsing the provided markdown files to extract the full epic and story inventory required for generating the tracking YAML.

What limitations should I expect when converting story headings to kebab-case status keys?

The primary constraint is that story headings must be convertible into kebab-case status keys, and the workflow requires file-based progress tracking across planning and implementation directories rather than a database backend.