bmad-sprint-planning
Skill2 starsChanged 2 months agoMITView on GitHub
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"
21 other projects use a version of this, 12 of them edited.
Adopted by
Most recently taken up by
- muslim-sec/skillstheir own version, first seen Nov 15, 2026
- snovak7/bmad-github-zoho-pipelineedited, first seen Nov 14, 2026
- delorenj/skillsedited, first seen Nov 7, 2026
- PaulKnauer/sonos-mcp-serveredited, first seen Oct 31, 2026
- MysterionRise/forgetestedited, first seen Oct 25, 2026
- laraxot/laravelpizza.comedited, first seen Oct 8, 2026
Used with
Projects with it also use bmad-investigate.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GauravRatnawatSkillbmad-investigate
Forensic case investigation with evidence-graded findings, calibrated to the input. Use when the user asks to investigate a bug, trace what caused an incident, walk through unfamiliar code, or build a mental model of a code area before working on it.
Also in 4 projects that use this
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 12
- paulpreibisch/AgentVibes★ 15520% same
- laraxot/laravelpizza.com★ 2620% same
- 2233admin/opencli-Razormind★ 1998% same
- DogaOztuzun/branchdeck★ 1820% same
- delorenj/skills★ 1797% same
- MysterionRise/forgetest★ 498% same
- mannnrachman/pi-bmad★ 299% same
- AvishkaGihan/ventureiq★ 120% same
- ChrisBP-Dev/portfolio★ 120% same
- PaulKnauer/sonos-mcp-server★ 197% same
2 more not listed
Wrote their own version · 9
- delorenj/mcp-server-trello★ 446same name
- marlonvidal/tech-manager-os★ 17same name
- mugsun/curdx-flow★ 4same name
- jeffrey2423/commit-like-pro★ 2same name
- muslim-sec/skills★ 1same name
- Tyler-Hughes312/mycelium★ 1same name
- Wellington-HMV/agentiq★ 1same name
- areesh-ali/AMKP★ 0same name
- GauravRatnawat/claude-cost-optimizer★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository184 other files it gives its agents.
- bmad-advanced-elicitationSkill
- bmad-agent-analystSkill
- bmad-agent-architectSkill
- bmad-agent-builderSkill
- bmad-agent-devSkill
- bmad-agent-pmSkill
- bmad-agent-ux-designerSkill
- bmad-architectureSkill
- bmad-bmb-setupSkill
- bmad-brainstormingSkill
- bmad-build-autoSkill
- bmad-buildSkill
- bmad-checkpoint-previewSkill
- bmad-code-reviewSkill
- bmad-correct-courseSkill
- bmad-create-architectureSkill
- bmad-create-epics-and-storiesSkill
- bmad-create-prdSkill
- bmad-create-storySkill
- bmad-customizeSkill
- bmad-deep-reconSkill
- bmad-dev-autoSkill
- bmad-dev-storySkill
- bmad-document-projectSkill
- bmad-domain-researchSkill
- bmad-editorial-review-proseSkill
- bmad-editorial-reviewSkill
- bmad-editorial-review-structureSkill
- bmad-edit-prdSkill
- bmad-eval-runnerSkill
- bmad-forge-ideaSkill
- bmad-generate-project-contextSkill
- bmad-helpSkill
- bmad-market-researchSkill
- bmad-module-builderSkill
- bmad-party-modeSkill
- bmad-prdSkill
- bmad-prfaqSkill
- bmad-product-briefSkill
- bmad-project-contextSkill
- bmad-qa-generate-e2e-testsSkill
- bmad-quick-devSkill
- bmad-retrospectiveSkill
- bmad-review-adversarial-generalSkill
- bmad-review-edge-case-hunterSkill
- bmad-reviewSkill
- bmad-review-verification-gapSkill
- bmad-specSkill
- bmad-sprint-statusSkill
- bmad-teach-me-testingSkill
- bmad-teaSkill
- bmad-technical-researchSkill
- bmad-testarch-atddSkill
- bmad-testarch-automateSkill
- bmad-testarch-ciSkill
- bmad-testarch-frameworkSkill
- bmad-testarch-nfrSkill
- bmad-testarch-test-designSkill
- bmad-testarch-test-reviewSkill
- bmad-testarch-traceSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Treat every entry in {workflow.persistent_facts} as foundational context for the rest of the run.
- Very specific: line 23
If interactive and unclear, ask.
- Distinctive: line 39
When invoked headless, do not ask.
“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow. On failure, read{skill-root}/customize.tomldirectly and use defaults. - Execute each entry in
{workflow.activation_steps_prepend}in order. - Treat every entry in
{workflow.persistent_facts}as foundational context for the rest of the run. Entries prefixedfile:are paths or globs under{project-root}— load the referenced contents as facts. All other entries are facts verbatim. - Load
{project-root}/_bmad/bmm/config.yaml(andconfig.user.yamlif present). Resolve{user_name},{communication_language},{document_output_language},{project_name},{planning_artifacts},{implementation_artifacts},{project_knowledge}(skip gracefully if unset),{date}. Stay in{communication_language}for every turn, not just the greeting. Greet
{user_name}, detect intent, and load only what that intent needs:- readiness — check implementation readiness only: load
references/readiness-gate.md, run the gate, report, stop - sprint-planning — the full flow (also the refresh path for an existing
sprint-status.yaml): loadreferences/readiness-gate.md, then on PASSreferences/generate-tracking.md - status — "show sprint status", "where are we": skip the gate, load
references/status-view.md - validate — check the tracking file's format: load
references/validate.md - fix — repair or rebuild a broken
sprint-status.yaml: loadreferences/fix-sprint-status.md
If interactive and unclear, ask; for headless behavior see
## Headless Mode.- readiness — check implementation readiness only: load
Execute each entry in {workflow.activation_steps_append} in order.
Activation is complete. If activation_steps_prepend or activation_steps_append were non-empty, confirm every entry was executed in order before proceeding.
If the Script Fails
This rule covers every intent: when sprint_plan.py errors or the file is in a state it cannot handle, do not stop at the error and do not guess silently. Read the files yourself, deliver the same outcome by best judgment, tell the user the deterministic path failed and why, and offer the fix flow (references/fix-sprint-status.md) to restore a file the script can work with.
On Completion
Whatever the intent, close out in {communication_language} per the loaded reference, then run {workflow.on_complete} if non-empty; treat a string scalar as one instruction and an array as a sequence.
Headless Mode
When invoked headless, do not ask. Run the gate and, unless intent was readiness-only, generate tracking. Ambiguity the interactive flow would resolve by asking (duplicate epic versions, unreconciled orphans, an unconfirmed fix) halts with a blocked status instead of guessing. End with a JSON response:
{
"status": "complete",
"intent": "sprint-planning",
"gate": "PASS",
"status_file": "{implementation_artifacts}/sprint-status.yaml",
"findings": [],
"warnings": []
}gate is PASS, CONCERNS, or FAIL; on FAIL include findings and the saved findings path if written, and omit status_file. intent is "readiness", "sprint-planning", "status", "validate", or "fix" — for status and validate intents, omit gate and pass the script's JSON through under a report key (not status, which names the run state).
References
scripts/sprint_plan.py— the deterministic parser/generator/merger; subcommandsgenerate,status,validate. Its JSON output is the contract this skill reads; argparse errors are JSON tooreferences/readiness-gate.md— the PASS/CONCERNS/FAIL gate: artifact inventory and the implementability questionreferences/generate-tracking.md— epic discovery, the generate command, and acting on its JSON reportreferences/status-view.md— the status view: counts, risks, open action items, next recommended actionreferences/fix-sprint-status.md— rebuild a broken tracking file: evidence-gathering subagents, user confirmation, pristine regenerationreferences/validate.md— format validation of an existingsprint-status.yamlsprint-status-template.yaml— the documented file format and status vocabulary; the script embeds the same block and the test suite pins the two copies together
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

