scope-gatelisted
Install: claude install-skill Snowfly0709/claude-scope-gate
# Scope gate
Every other check answers *"is this diff good?"*. This one answers *"is this the
right diff?"* — and explains the answer to someone who may not read code.
Run it before writing code. Run it again before opening a PR if the shape
changed. It ends by **stopping and asking**; it never approves silently and never
decides for the user.
Read `.claude/scope-gate/invariants.md` first. If it is missing, say so and
suggest `/scope-gate-setup` — then continue with steps 1–3 and the two
structural tests, which work without it.
---
## Step 1 — Restate the outcome, in the user's words
One sentence: **what the user will be able to observe** when this is done.
Their words, not the problem class. "I want to hear Hokkien" is the outcome.
"Integrate a TTS provider" is a solution already chosen — if you restate it that
way, the gate is dead on arrival because every option you generate will be a
variation of that solution.
If the request genuinely is the general capability, say so explicitly. Some asks
really are "build the integration," and the gate should not pretend otherwise —
it just changes which questions matter (skip to the structural tests).
## Step 2 — Find the smallest thing that produces that outcome
List real options. **At least one must involve no code at all.** If you cannot
find a zero-code option, say what you ruled out and why — "no configuration
reaches this" is a finding, not a formality.
Zero-code options that keep turning out to be the answer:
- Crea