layer-cyclelisted

# Layer cycle <!-- harness:claude-code --> In Codex, first read [Codex distribution](../delegation/references/dispatch-knobs.md#codex-distribution) for installed role setup, native dispatch, isolation prerequisites, and completion routing. That section supplies the Codex procedures wherever this workflow names Claude Code tools. <!-- /harness --> Quality is layered, not single-pass. This skill is the L1 orchestrator: it owns the contract, the rubric, and the cycle budget, and is the only level that knows layering exists. Workers get discrete briefs; findings flow up, intentions flow down, nothing else crosses levels. This is the manager's standard cycle — **build → review → revise → simplify** — formalized: create is build, evaluate is review, refine is revise plus simplify (`deletion-pass`). A manager runs the lightweight form on every building link by default; invoke this skill when the link is a whole module and needs budgets, triage, and stop conditions. ## Inputs (ask only for what's missing) **target**, **contract**, **rubric**, **gate**; optional cycle budget (default 3) and effort level. ## Process, per cycle 1. Verify the gate. Red → dispatch a fix brief before anything else. 2. **Evaluate** — size the check to the diff, not the process: - **Trivial** (~10 changed lines or fewer, confined to one file, no interface change) → spot-check it yourself against the contract; confirm the fix addresses an observed-red case. No agent dispatch. - **Bounde