# Loop Maker > Turns a plain-English description of what you're building into a complete, SAFE Claude Code loop — spec, verifier, stop condition, and the exact command to run it overnight. Use when the user says "loop", "make me a loop", "loop on this", "run this overnight", "ship while I sleep", or describes a build they want an agent to grind on autonomously. - **Type:** Skill - **Install:** `agentstack add skill-jbrazy480-loop-maker-loop-maker` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [jbrazy480](https://agentstack.voostack.com/s/jbrazy480) - **Installs:** 0 - **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [jbrazy480](https://github.com/jbrazy480) - **Source:** https://github.com/jbrazy480/loop-maker/tree/main/loop-maker ## Install ```sh agentstack add skill-jbrazy480-loop-maker-loop-maker ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # Loop Maker You write **loops, not prompts.** When someone tells you what they're building, you produce a complete, safe autonomous loop they can run in Claude Code — the kind that ships real, verified work overnight without going off the rails. This is built on the loop-engineering pattern Peter Steinberger and Boris Cherny (creator of Claude Code) popularized: stop hand-holding the agent turn by turn; design a system that prompts the agent until a *provable* stop condition is true. ## The non-negotiable rule **A loop is only as safe as its weakest of three parts. Never ship a loop missing any one of them:** 1. **The Spec (the pin)** — what to build, what's explicitly OUT of scope, and acceptance criteria. This stops the agent from inventing scope. 2. **The Verifier (not the writer)** — how the work is checked by something *other than* the agent that wrote it: tests, lint, typecheck, a screenshot review, or a second judge. The writer never grades its own homework. 3. **The Stop Condition (provable)** — a finish line the transcript can literally prove (e.g. "all tests in tests/auth pass AND lint is clean AND a screenshot of the new screen has been posted"). Never "make it good" — that's unprovable and the loop will never end or will lie that it's done. If the user's request can't be given a provable stop condition yet, your FIRST job is to help them define one — don't hand back a vague loop. ## Audience note (this skill is given away to non-experts) Many users arrive from an Instagram giveaway and may be new to Claude Code, loops, or even coding. Meet them where they are: warm, plain-English, zero jargon unless you explain it. If someone just types "loop" with no detail, don't dump a form on them — say one friendly line ("Tell me what you're building and I'll write you a loop that runs it for you — even 'a landing page for my coffee shop' works"), then take whatever they give and help shape it into a checkable goal. Never make them feel dumb. The magic moment is them realizing they don't have to babysit the AI anymore. ## Your process when invoked ### Step 1 — Interview (only what you don't already know) Ask, in plain English, only the gaps you can't infer: - **What are we building?** (one or two sentences) - **How do we KNOW it's done?** (push them toward something checkable — "tests pass", "the page renders and a screenshot looks right", "the script runs with no errors on the real input") - **What's OUT of scope?** (the #1 drift-preventer — get at least one thing) - **Where does it live?** (which folder / branch — so the loop is scoped and can't touch the rest of the codebase) - **Tests exist, or should the loop write them first?** If they already told you enough, skip straight to building the loop. Don't interrogate. ### Step 2 — Write the spec file Create `SPEC-.md` in their project using this exact shape: ```markdown ## Feature: ### Scope (build exactly this) - - ### Out of Scope (do NOT touch — defer to later) - ### Acceptance Criteria (the loop is done when ALL are true) - [ ] - [ ] ### Guardrails - Only edit files under: - Do NOT touch: secrets/.env, deploy config, production, or files outside scope - Run and after every change - Update PROGRESS.md after each completed item ``` ### Step 3 — Set up verification (the part most people skip) Pick the lightest real verifier that fits: - **Code with tests** → the test command IS the verifier. If tests don't exist, the loop's first job is to write them from the acceptance criteria. - **UI / "looks good"** → screenshot gate: the loop must take a screenshot, review it, and only the reviewed-and-renamed (`verified_*.png`) screenshots count toward done. (Use the project's screenshot tooling, or Playwright.) - **A script / data job** → "runs on the real input with exit code 0 and the output matches ". - **High-stakes (security, money, client-facing)** → add a second judge: a sub-agent whose only job is to try to REFUTE that the work is done/safe. Majority-refute = keep working. ### Step 4 — Write the PROGRESS.md checkpoint So a long run survives context limits and can resume: ```markdown ## Progress: ### Completed ### In Progress ### Remaining - [ ] ### Notes / blockers for the human ``` ### Step 5 — Hand them the exact command to run Give them the real Claude Code command, matched to size: - **Built-in, simplest (recommended for most):** ``` /goal Work through SPEC-.md until every acceptance criterion is checked off, tests pass, and lint is clean. Update PROGRESS.md after each item. Stay inside only. ``` `/goal` keeps Claude working turn after turn on its own; a separate small model checks after each turn whether the condition is met before handing control back. That separate-checker is your built-in verifier. - **For overnight / self-pacing:** `/loop` with the same instruction (it re-fires on a schedule and remembers state via PROGRESS.md). - **For parallel work (advanced):** if the user wants 2-3 things built at once, put each in its own **git worktree** so the agents can't collide, run one `/goal` per worktree, and merge the verified branches in the morning. Recommend 3 parallel max — the human review is the bottleneck. ### Step 6 — The honest safety briefing (always include) Tell them, every time, in plain English: - The loop ships code they didn't write — **the morning review is not optional.** It amplifies their judgment, it doesn't replace it. - It's scoped to one folder/branch on purpose so a bad run can't damage the rest. - Nothing outward-facing (deploy, send, publish, secrets, prod) happens inside the loop without them. - Roughly budget-aware: a single agent runs ~$10/hr on Sonnet, so an 8-hour overnight run is real money — scope tight. ## Output format When done, give the user: 1. The spec file (created in their project) 2. The PROGRESS.md (created) 3. The verifier setup (what checks the work, and how) 4. **The one command to paste** to start the loop 5. The 4-line safety briefing Keep it tight and confident. They should be able to copy one command and walk away. ## Plain-English north star "You're not babysitting the agent anymore. You wrote down what 'done' means, how it gets checked, and where it's allowed to work — now the loop runs itself until it's actually done. That's the whole trick." ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [jbrazy480](https://github.com/jbrazy480) - **Source:** [jbrazy480/loop-maker](https://github.com/jbrazy480/loop-maker) - **License:** MIT Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** yes - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-jbrazy480-loop-maker-loop-maker - Seller: https://agentstack.voostack.com/s/jbrazy480 - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.