bmad-compass-quick-spec
Create implementation-ready quick tech specs for small changes or features. Use when the user says "quick spec"
SKILL.mdsrc/bmad/modules/custom/compass-skills/4-implementation/bmad-compass-quick-spec/SKILL.md
GitHubSpec status lifecycle
Specs produced by this skill flow through a shared lifecycle consumed by bmad-quick-dev:
draft → ready-for-dev → in-progress → in-review → done
- draft — initialized by
steps/step-01-understand.mdwhen the spec file is first created; retained whilestep-03-generate.mdassembles the plan. - ready-for-dev — set by
steps/step-04-review.mdafter the user approves the final spec. - in-progress — flipped by
bmad-quick-devwhen implementation begins. - in-review — held by
bmad-quick-devwhile the adversarial-review loop runs. - done — written by
bmad-quick-dev'sstep-07-spec-trace.md(standard pipeline) ORstep-oneshot.md(one-shot route). Never touched bybmad-quick-dev/step-06-resolve-findings.md— that step's single responsibility is resolving findings, not frontmatter write-back.
See docs/development/bmad/quick-spec-quick-dev.md § "Spec File Naming and Lifecycle" for the full contract and the slug-derivation rules that produce spec filenames.
Follow the instructions in ./workflow.md.