script-the-deterministic-worklisted

Re-anchor the discipline that purely deterministic sub-work — counting, diffing, sorting, transforming, matching, sweeping, arithmetic — gets a script that runs and returns real output, and the model reasons only afterward over that output — then audit the work in flight for transforms executed by hand and re-derive them from a script's result. Use when: 'script the deterministic work', 'you should have scripted that', 'don't eyeball that', 'you counted that by hand', 'compute that, don't estimate', 'diff it with a tool', 'stop hand-tallying', 'run it instead of guessing', or at conversation start on count-, diff-, or transform-heavy work. Not for authoring a requested script or migration ('script it' as a work order is script-writing, not this corrector), and not for a first-turn count/diff/transform work order ('diff these files', 'count the routes', 'convert all of these') — doing that task with a tool is just doing the task; this corrector fires on drift, mid-flight or retrospective, or as posture at the
melodic-software/claude-code-plugins · ★ 13 · AI & Automation · score 79

Install: claude install-skill melodic-software/claude-code-plugins

# Script the deterministic work A drift corrector for the discipline of offloading deterministic sub-work to a script instead of performing it in your head. The method — re-anchor, audit the work in flight, correct forward, report, and the tone that firing this is not an accusation — lives in [`${CLAUDE_PLUGIN_ROOT}/context/re-anchor-audit-correct.md`](../../context/re-anchor-audit-correct.md). Read it; this file adds only what is specific to scripting deterministic work. ## The discipline this re-anchors When a sub-task is purely deterministic — its answer follows mechanically from its input with no judgement in the middle — write a script (or invoke a tool) that produces the answer, run it, read the output, and reason only **after**, over that output. Counting, diffing, sorting, transforming, matching, sweeping across files, and arithmetic are the recurring shapes. The model is a poor calculator and a worse line-counter; a hand-tallied count or an eyeballed diff carries a silent error the script would not. The boundary of *what* to script is not "anything tedious" — it is set by which enforcement tier the sub-work belongs to. ### The tier vocabulary — a standards convention owns this The source of truth for the tier distinction is the consuming organization's enforceability-tiers convention, which classifies work by who can decide it. Resolve it per the method doc's ladder — the consumer's own instruction layer first, then that standards convention, then the portable