loop-builderlisted

Build a file-based agent loop (harness) for a long, powerful task BEFORE running it — so you design the loop and only verify the output, instead of supervising every step. Runs a short interview (goal, done-condition, non-goals, verify commands), scaffolds loops/<slug>/ with VISION.md + specs + IMPLEMENTATION_PLAN.md + AGENTS.md + PROMPT files + loop.sh, runs PLANNING, gets ONE plan approval, then loops BUILDING autonomously and hands back the diff + eval results. Trigger when the user says "loop-builder", "/loop-builder", "build a loop", "create a loop for X", "set up an autonomous loop", or asks to run a long autonomous task (a feature, a refactor, a tool, a content batch).
criscatalyst/loop-builder · ★ 2 · Web & Frontend · score 75

Install: claude install-skill criscatalyst/loop-builder

# /loop-builder — design the harness, then run the loop Stop prompting an agent step by step. Instead, define the **goal** + a **verifiable done-condition**; this skill generates the whole file-based harness on disk and then runs the loop. You only verify the output. **Promise:** from "I babysit every step in case it errors" → "I approve a plan, then I verify the result." This is **loop engineering**: the leverage is no longer the single prompt, it's the system that prompts, runs, and *verifies* the agent until the goal is met. See `README.md` for the full background and credits. ## When to use - A long, powerful task: a new feature, a big refactor, a new tool/script, a content batch, a migration. - The user says: "build a loop", "create a loop for X", "set this up to run on its own", "/loop-builder". Do NOT use for: 5-minute one-shots, tasks with no objective done-condition, pure-judgment decisions, or single irreversible actions (those stay direct-confirm). ## Guiding principles (loop engineering) 1. **State lives on disk, not in context.** Each iteration starts from fresh context and reloads the files. 2. **VISION.md does not change** during the run (the compass). The PLAN changes (the task order). 3. **Backpressure beats direction:** wrong output is rejected by an automatic eval-gate (tests/lint/build), not by the human. 4. **Maker/verifier split:** the agent that builds ≠ the agent that verifies (models skew positive grading their own work). 5. **Ratchet:** every