bmad-sprint-planning

Generate sprint-status.yaml from epic markdown files for Scrum tracking.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-sprint-planning-amitmishra-byldd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/amitmishra-byldd/Bmad-Note-Maker/tree/main/_bmad/bmm/4-implementation/bmad-sprint-planning
Command: npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-sprint-planning-amitmishra-byldd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation and maintenance of a sprint-status.yaml by parsing epic markdown files, extracting epics and stories, and detecting current story implementation states so teams no longer manually assemble or reconcile sprint tracking data.

Core Features & Use Cases

  • Epic and Story Discovery: Finds whole or sharded epic documents using flexible name patterns and builds a complete inventory of epics, stories, and retrospectives.
  • Status Detection & Preservation: Detects story files to upgrade statuses, preserves existing advanced statuses, and enforces an ordered structure of epic → stories → retrospective.
  • Validation & Output: Generates a documented YAML sprint-status file in the configured implementation artifacts location and runs checks to ensure all epics/stories are accounted for and the file is valid YAML.
  • Use Case: Run during sprint planning to produce a single source-of-truth YAML file for Scrum Masters to track progress across multiple epics and stories.

Quick Start

Run the sprint planning workflow to generate sprint-status.yaml from the project's 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 sprint status YAML from epic markdown files for Scrum tracking?

Sprint status YAML is generated by scanning a repository's planning artifacts to extract epics, stories, and retrospectives into a structured inventory. The Skill detects story file presence to upgrade statuses and outputs a valid sprint-status.yaml file for ongoing team tracking.

What is the best way to automate sprint planning status tracking across multiple epics?

Automating sprint planning status tracking involves parsing epic markdown files to build a complete inventory of epics, stories, and retrospectives. This process detects story implementation states and preserves existing advanced statuses to maintain a single source-of-truth YAML file for Scrum Masters.

How does story status detection work when updating a sprint-status.yaml file?

Story status detection works by checking for story file presence to upgrade statuses, while preserving any existing higher statuses that were already recorded. It enforces an ordered structure of epic to stories to retrospective to ensure all planning artifacts are accounted for in the output.

Can I use sharded epic documents to generate sprint tracking data?

Yes, sharded epic documents are supported during epic and story discovery. The Skill uses flexible name patterns to find whole or sharded epic markdown files and builds a complete inventory of all epics, stories, and retrospectives from them.

Does sprint planning automation validate the generated YAML inventory?

Yes, the generated YAML inventory is validated by running checks to ensure all epics and stories are accounted for and the output file is valid YAML. The validated sprint-status.yaml is then written to the configured implementation artifacts location.

When should I not use automated sprint planning YAML generation?

Automated sprint planning YAML generation is specifically designed for Scrum teams working with epic markdown files and story tracking. It may not suit workflows that do not maintain planning artifacts in markdown or do not utilize an epic to stories to retrospective ordered structure.