bmad-sprint-planning

Validates planning readiness and generates sprint-status.yaml tracking files from epic documents.

1|Updated Sep 18, 2026
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill bmad-sprint-planning-pastasus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-sprint-planning
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/bmad-sprint-planning
Command: npx skills add https://github.com/PastaSus/egg-defender --skill bmad-sprint-planning-pastasus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ruamel.yaml, and includes scripts (resource) and references (resource) components.

What problem does it solve? Agile teams need a reliable way to confirm their planning artifacts are complete enough to build from, and a consistent machine-readable file to track epic and story progress across a sprint. This Skill gates implementation readiness, then generates, summarizes, validates, and repairs the sprint-status.yaml tracking file. ## Core Features & Use Cases - Readiness Gate: Scans planning artifacts (briefs, PRDs, architecture, epics) and delivers a PASS/CONCERNS/FAIL verdict on whether the plan is implementable. - Deterministic Tracking Generation: Parses epic files into kebab-case story keys and writes sprint-status.yaml via a Python script with atomic writes, status preservation, and legacy v6 status normalization. - Status, Validate, and Fix Flows: Summarizes sprint progress with risks and next recommended actions, validates file structure, and rebuilds broken tracking files with user-confirmed status inference. - Use Case: After drafting epics for a new project, ask the assistant to run sprint planning — it checks readiness, generates sprint-status.yaml, and later answers "where are we" with counts, risks, and the next story to build. ## Quick Start Ask the assistant to run sprint planning to check implementation readiness and generate the sprint status file from your epics.

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 documents?

Run the sprint planning flow, which parses epic markdown files for Epic and Story headings, derives kebab-case keys, and writes sprint-status.yaml via the sprint_plan.py generate subcommand. Existing statuses are preserved and never downgraded during regeneration.

How do I check if my project plan is ready for implementation?

Use the readiness intent, which inventories planning artifacts like briefs, PRDs, architecture, and epics, then issues a PASS, CONCERNS, or FAIL verdict. FAIL findings name the skill that fixes each gap and can be saved to implementation-readiness.md.

Can I validate or repair a broken sprint-status.yaml file?

Yes. The validate subcommand reports structural problems without writing, and the fix flow infers the true state from epic files, story files, and git history, confirms it with you, then rebuilds the file with --fresh and --set flags.

Does the script handle legacy v6 status values like drafted or contexted?

Yes. Legacy statuses are normalized on every read: drafted maps to ready-for-dev and contexted to in-progress. They are reported in the legacy_mapped field and never reset, so progress is preserved across regenerations.

What happens if the sprint planning script fails on my files?

The skill instructs the assistant to read the files directly, deliver the same outcome by best judgment, explain why the deterministic path failed, and offer the fix flow to restore a file the script can handle.