stage-gate
Installation
SKILL.md
Stage gate
Reviews your work at the three points where problems are cheapest to catch: the plan before code is written, the diff before it is pushed, and the repo after the merge. Each gate is run by a fresh reviewer rather than the author, and the release gate turns what was learned into rules while keeping CLAUDE.md or AGENTS.md short.
| Gate | Run it when | It checks | Writes |
|---|---|---|---|
--plan |
a plan exists, no code written yet | assumptions, ambiguity, simpler paths, runnable success criteria | no |
--dev |
code is written, not yet pushed | every hunk traces to the request | no |
--release |
the branch is merged or released | lessons captured, memory file lean and armed | yes |
Run each gate at its boundary even when the work looks finished. That is the moment the gate is for, and the moment it is easiest to skip.
Picking a gate
An explicit flag wins. With no flag, infer from state — then say which gate you picked and why before running it:
- uncommitted or unpushed diff →
--dev - no diff, but a plan in the conversation or a recent plan file →
--plan - clean tree on the default branch →
--release