A Claude Code plugin that turns ambiguous work into shipped, tested, serialized artifacts through evidence-gated loops. Not a prompt library — a stateful consequence engine. Plus a bounded /ratchet-evolve mutation loop. Mutate. Test. Keep the delta.
The pre-PR hostile pass for torque-loop. Runs scripts/preflight.js for the deterministic checks (tests, version alignment, dependency gate, leak scan, trace tags) then applies human judgment to the checks a script can't rule on (testless changes, prose-enforcement, diff minimality, parked-decision creep, scope…
Cut a Torque Loop release end-to-end and stop at the PR — branch, bump all five version fields, promote the CHANGELOG with lineage + slogan, verify with npm test + doctor, commit chore(release). Use when [Unreleased] has earned a version. Never merges, tags, or publishes a Release; those are Danny's.
Add or evolve a /ratchet: command across every synced surface at once — canonical prompt in PROMPTS.md, SKILL.md in the house shape, README row, templates, drift guard, tests. Use when a new loop move is being added to the plugin (like map or the probe were), or an existing skill's contract is changing. Prevents the…
Run adversarial review on a finished-looking artifact. Use to replace self-praise with hostile pressure before shipping. Convenes a five-voice review board (impatient user, competitor, maintainer, auditor, saboteur), returns concrete failure modes with severity and evidence demanded, and the smallest patch each…
Rank the real blockers by leverage and pick the one bottleneck to attack. Use when there are many possible next moves and you risk doing interesting-but-not-advancing work. Scores obstacles by Leverage × Certainty × Speed-to-unblock × Risk-of-ignoring and names the winner and why it beats the tempting alternative.
Kill or park the options that are quietly draining energy. Use when you are carrying option debt — too many open possibilities, none advancing. Returns a kill / park / keep table, why each option is attractive, what fear keeps it alive, what gets simpler if it dies, and one option to burn right now.
Serialize the current session into durable state — the breadcrumb the next session resumes from. Use at the end of a work session or after any real advance. Returns working title, objective, decisions, artifacts, defects/risks, open loops, next action, next command, retrieval tags, and a one-sentence memory. Only…
Attack the hidden assumptions that could make the current plan look stupid in hindsight. Use before committing effort to a direction. Returns the load-bearing assumptions, how each breaks, the signal that would reveal the break, and the cheapest test to falsify it — then the top three kill-tests to run now.
Force a single defended choice instead of a menu of options. Use when analysis has produced alternatives but no commitment. Scores options on upside, reversibility, time-to-feedback, strategic compounding, cost-of-being-wrong, and unlock value; returns the chosen path, the most tempting rejected path and why it loses…
Evolve one artifact through a bounded, evidence-gated mutation loop — lock target, snapshot baseline, apply one pressure, generate candidate deltas, judge, patch, verify, keep or revert, record state, and name the next edge. Not brainstorming and not a general 'make this better': every kept change must be proven. Use…
Produce a compact handoff for another model, agent, teammate, or future session. Use when work must transfer without losing state. Returns a self-contained brief — objective, what's done, what's decided, what's open, the exact next action, and the context needed to act — compressed so the receiver can start…
Run the full consequence loop on any messy task, project state, prompt pile, codebase goal, or vague direction. Use this when you do not know which Ratchet command to use. Locks a target, ranks blockers, cuts assumptions, builds the smallest artifact, attacks it, patches failures, and serializes state — ending with…
Convert vague input into a locked, executable target. Use when a task is fuzzy, over-broad, or stated as a wish. Returns the literal object, operation, output shape, real outcome, proof-of-done, smallest progress artifact, the highest-information missing variable, and the assumption to adopt if it stays missing.
Run recursive improvement — build → attack → patch → compile — until the artifact is genuinely done. Use to drive an artifact to a stable, tested, serialized state without stopping at the first draft. Repeats the cycle and reports an iteration log and confidence score, stopping only when no critical/high defect, no…
Map the fog before you build. Use when uncertainty is high (aperture A3–A4), the terrain is unfamiliar, the taste is "I'll know it when I see it", or you are porting a reference implementation. Walks the task through four unknown-quadrants — known knowns (settled ground with file evidence), known unknowns (one…
Name the mechanism when a situation feels confusing. Use to cut through a tangle to the one causal handle. Separates surface symptoms from the underlying mechanism, the constraint causing it, the feedback loop keeping it alive, and the highest-leverage intervention point — then the action that changes the mechanism…
Fix only what failed — nothing else. Use after an attack surfaced defects, to prevent the model from rewriting everything for elegance. Returns the minimal delta under REMOVE / ADD / CHANGE, the patched artifact, the relevant retest result, and any defects still open.
Audit a prompt library as an operating system, not a pile of prompts. Use to find what a prompt collection over-does, under-does, and where it leaks into meta-looping. Classifies each prompt by the work it performs, finds overrepresented and missing moves, flags prompts that cause meta-loops or never produce…
Push the boundary after a safe version already exists. Use to find the boldest adjacent move that could multiply the result without turning it into fantasy. Returns the safe default, the boundary-pushing path, why it might work, why it might be stupid, the cheapest experiment that distinguishes them, the version to…
Create or update the canonical feature / test / defect ledger for a codebase. Use to turn a repo into a durable quality record that survives sessions. Maintains features (with evidence), tests (with status), and defects (with severity) via the ratchet CLI so quality state is queryable, not remembered.
Discover user-facing features, workflows, routes, APIs, configs, and tests in a codebase by evidence, not guesses. Use to turn an unfamiliar or under-documented repo into an inventory of what actually ships. Returns features with code evidence, undocumented screens/routes/workflows, APIs and state transitions needing…
Read the current ratchet state so the loop doesn't rediscover itself. Use to orient at the start of a session or between moves. Returns the current objective, active artifact, last decision, open defects, confidence, next recommended command, and a staleness warning if work changed without a compile.
Run a change (or an artifact) through a test harness built to embarrass it, then record the results as defects. Use instead of asking whether the work is good — never self-grade. Builds acceptance / happy-path / edge / abuse / ambiguity / regression tests plus fake-progress red flags, runs the artifact through them…