invariants
Installation
SKILL.md
invariants
Some pairs of actions have a required order, and some claims require evidence before they may be made. Getting either wrong rarely produces a loud error — the second step just quietly means less than it appears to.
These are stated here once. Commands reference this skill and carry only the rule specific to them.
What is actually enforced
Be precise about this, because the difference matters most in exactly the conditions where it is easiest to forget: a long session, a tired user, a model under context pressure.
| invariant | how it holds |
|---|---|
| PLAN → BUILD | hook — the edit is blocked (plan-gate.sh) |
| VERIFY → DEPLOY | hook — the deploy command is blocked (deploy-gate.sh) |
[deployed] rows only flipped by SMOKE |
hook — the edit is blocked (acceptance-gate.sh) |
| RED → GREEN | asked |
| evidence before a check is ticked | asked |
| no row vanishes from a workflow result | code, in the workflow scripts |