skills.rest
b566776
b566776COMMUNITY
Explore all skills by this author →
GitHub

bmad-sprint-planning

Generate sprint-status.yaml from epic*.md files with statuses and timestamps.

Updated May 5, 2026
Search Tags:#workflow#planning#epics#yaml#sprint#status-tracking
One-click install
npx skills add https://github.com/b566776/whitebox --skill bmad-sprint-planning-b566776
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/b566776/whitebox/tree/main/.gemini/skills/bmad-sprint-planning
Command: npx skills add https://github.com/b566776/whitebox --skill bmad-sprint-planning-b566776

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint planning often lacks a single source of truth. This skill automates generating and maintaining a consolidated sprint status from epic documents, reducing manual updates and misalignment.

Core Features & Use Cases

  • Generate sprint-status.yaml by aggregating epics and stories from epic*.md files.
  • Detect and reflect current statuses (backlog, ready-for-dev, in-progress, done) with automatic updates while preserving manual adjustments.
  • Validate consistency between epics and status entries across multiple epics for reliable reporting.

Quick Start

Run sprint planning to generate or update sprint-status.yaml from all epic files in the configured epics directory.

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 tracking from epic files?▼

Generate sprint status tracking by parsing epic*.md files to extract stories and statuses, outputting a consolidated sprint-status.yaml file with generated timestamps, project metadata, and status mappings for reporting.

What is the best way to maintain a single source of truth for sprint planning?▼

The best way to maintain a single source of truth for sprint planning is to automate generating a consolidated sprint status from epic documents, reducing manual updates and preventing team misalignment.

How does sprint planning detect story statuses like backlog and in-progress?▼

Sprint planning detects story statuses like backlog, ready-for-dev, in-progress, and done directly from epic files, applying automatic updates to the sprint-status.yaml while preserving any manual adjustments.

Does sprint planning validate consistency between epics and status entries?▼

Yes, sprint planning validates consistency between epics and status entries across multiple epic files, ensuring reliable reporting and preventing misalignment within the generated sprint-status.yaml.

Can I use sprint planning for projects with stories defined in markdown files?▼

Yes, you can use sprint planning for projects with epics and stories defined in epic*.md files, as it loads project configuration, detects statuses, and outputs structured YAML with project metadata.

What format does sprint planning output for status reporting?▼

Sprint planning outputs a structured sprint-status.yaml file containing generated and last_updated timestamps, project metadata, and status mappings for consolidated visibility and reporting.

Related Skills

Explore More Software Engineering Skills→
ImaginerLabsImaginerLabs

bmad-sprint-planning

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

Official
Advanced
MazenMradMazenMrad
1

gds-sprint-status

Summarize sprint status and surface risks from sprint-status.yaml.

Community
Advanced
ldk-hubldk-hub

bmad-sprint-planning

Generate sprint-status.yaml from epic files with status detection and validation.

Community
Advanced
allaydesaiallaydesai
2

bmad-sprint-planning

Parse epic and story markdown files to generate sprint-status.yaml summaries.

Community
Intermediate