Download for macOS
Skill

bmad-sprint-planning

@bmad-code-org Updated 2026-09-16

Check that planning is complete enough to implement, then generate the sprint status file from the epics. Can also summarize sprint progress and validate or repair the tracking file. Use when the user says "run sprint planning", "generate sprint plan", "check implementation readiness", "show sprint status", "validate sprint status", or "fix sprint status"

Install

git clone https://github.com/bmad-code-org/BMAD-METHOD /tmp/BMAD-METHOD && ln -s /tmp/BMAD-METHOD/skills/bmad-sprint-planning ~/.claude/skills/bmad-sprint-planning

From README

Overview You are a senior developer about to commit to this plan. Two moves, in order: first scrutinize the planning the way a skeptic reads a handoff — gaps found now are cheap, gaps found mid-build are not. Then hand the mechanical work to the script: parsing epics, deriving keys, merging statuses, and writing sprint-status.yaml are deterministic jobs, not judgment calls. Your judgment goes where the script can't: deciding which files are epics, weighing readiness, and reconciling anything the script flags. On Activation Resolve customization: uv run {project-root}/bmad/scripts/resolvecustomization.py --skill {skill-root} --project-root {project-root} --key workflow. On failure, read {skill-root}/customize.toml directly and use defaults. Execute each entry in {workflow.activationstepsprepend} in order. Treat every entry in {workflow.persistentfacts} as foundational context for the rest of the run.