skills.rest
Asygnuz-S-A-S
Asygnuz-S-A-SOFFICIAL
Explore all skills by this author →
GitHub

bmad-sprint-planning

Generates sprint-status.yaml tracking files by parsing epic and story markdown documents.

Updated May 22, 2026
Search Tags:#epics#agile#yaml#sprint planning#user stories#backlog#status tracking
One-click install
npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-sprint-planning-asygnuz-s-a-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/Asygnuz-S-A-S/one-star/tree/main/.claude/skills/bmad-sprint-planning
Command: npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-sprint-planning-asygnuz-s-a-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agile teams using file-based planning lose track of which epics and stories are backlog, in-progress, or done. This Skill automates the creation and maintenance of a sprint-status.yaml file by scanning epic markdown files and detecting story statuses from the filesystem. ## Core Features & Use Cases - Epic and Story Parsing: Discovers whole or sharded epic documents (epics.md, epic-1.md, etc.) and extracts every epic, story, and retrospective entry. - Intelligent Status Detection: Upgrades stories to ready-for-dev when story files exist, while preserving more advanced existing statuses and never downgrading. - Structured YAML Output: Generates a validated sprint-status.yaml with documented status state machines for epics, stories, and retrospectives. - Use Case: After writing your product epics in markdown, run sprint planning to produce a complete tracking file that developers and agents update as work progresses. ## Quick Start Ask the assistant to run sprint planning and generate the sprint status file from your epic documents.

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 file from epic markdown documents?▼

Run the sprint planning workflow, which scans your planning artifacts directory for files matching *epic*.md, extracts all epics and stories, and writes a sprint-status.yaml with detected statuses to your implementation artifacts folder.

How does sprint status detection work for stories?▼

The workflow checks whether a story markdown file exists in the stories directory. If found, the story status upgrades from backlog to at least ready-for-dev, but existing more advanced statuses like in-progress or done are never downgraded.

Can it handle sharded epic files split across multiple documents?▼

Yes. If no whole epics.md file exists, it looks for an epics/index.md and reads every listed epic section file, combining all content so sprint status coverage remains complete across sharded documents.

What statuses are supported in the sprint-status.yaml file?▼

Epics use backlog, in-progress, and done. Stories use backlog, ready-for-dev, in-progress, review, and done. Retrospectives toggle between optional and done. All entries follow these state machine definitions.

Why is my story status not updating when I rerun sprint planning?▼

The preservation rule prevents downgrades: if the existing sprint-status.yaml records a more advanced status than the auto-detected one, the advanced status is kept. Statuses only move forward through the defined flow.

Related Skills

Explore More Product & Management Skills→
ImaginerLabsImaginerLabs

bmad-sprint-planning

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

Official
Advanced
AhmedKaram50AhmedKaram50

bmad-sprint-planning

Generate sprint-status.yaml from epic markdown files with status tracking.

Community
Intermediate
baobao0303baobao0303
1

harness-agent-ux-designer

Translates user needs into UX design and specification documents.

Community
Intermediate
Lobbi-DocsLobbi-Docs
18

jira

Automate Jira issue, sprint, board, and workflow tracking via API.

Official
Intermediate