back
loading skill details...
Enforces completion discipline for substantial autonomous work by writing acceptance gates before execution, decomposing work with the Depth Tree, running…
Unlazy Make incomplete work visible and make completion testable. Prove outcomes against a ledger instead of relying on a confident done report. Write gates before real work For solo work, create GATES.md from the local file templates/gates-leaf.md before implementing (orchestrated mode instead starts from templates/PLAN.md plus per-leaf templates/gates-leaf.md and per-branch templates/gates-node.md under .unlazy/<scope>/; see Build the Depth Tree below). State one observable outcome per gate. Give every runnable gate an indented CHECK: and EXPECT:; use a manual gate only when no command can decide the outcome. Throughout this file, <skill-dir> is the directory containing this SKILL.md and <scope> is a pipeline id under .unlazy/. Treat CHECK: as code. Before executing an inherited ledger, parse it without running anything and read every command and called script: node <skill-dir>/scripts/gate-check.mjs --status GATES.md Approve only commands you wrote or understand, then run them explicitly:
don't have the plugin yet? install it then click "run inline in claude" again.