Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aj-geddes/bmad-spec
Distills ANY messy input — brain dump, transcript, long PRD, stakeholder notes, feature request, voice memo — into a tight five-field SPEC.md kernel that any downstream planning skill can consume. The five fields are: Problem, Capabilities, Constraints, Non-Goals, Success Metrics.
Passed 15 of 21 test cases with the skill, and 8 of 21 without it.
and 11 more in the full report
10 fixed6 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to write out our finalized SPEC.md document. There is no config file present in the bmad-output directory. Where should the specification file and decision log be written by default?
| Checked | Without skill | With skill |
|---|---|---|
| Response uses bmad-output/SPEC.md as the default file output path. | Passed | Passed |
| Response uses bmad-output/decision-log.md as the default log path. | Missed | Passed |
The instructions your model reads when the skill loads.
Function: Accept messy, unstructured, or verbose input and produce a lean
SPEC.md kernel (five fields, no more) that anchors every downstream planning
workflow. This is a planning skill. It never writes application code, runs
tests, or builds anything.
A single file under the configured output folder (default bmad-output/):
bmad-output/
└── SPEC.md # the five-field kernel
The kernel is intentionally small — a SPEC is not a PRD, not a brief, not an architecture doc. It is the shared definition of what is being built and why. Every downstream skill (PRD, tech-spec, architecture) loads it as the ground truth for scope.
| Field | Purpose |
|---|---|
| Problem | The one thing that hurts right now and why it matters |
| Capabilities | What the solution must be able to do (outcome-framed) |
| Constraints | Hard limits that are not negotiable (budget, tech, time, compliance) |
| Non-Goals | Scope that is explicitly out — prevents creep and confusion |
| Success Metrics | Observable signals that confirm the problem is solved |
See templates/spec.template.md for the exact template with guidance and examples.
Accept whatever the user hands over:
Read it)test cases passed, vs 8 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.