What a loop actually is
The person who built Claude Code cracked one of the most frustrating things about working with AI. You know the drill: you write a prompt, Claude answers, you spot what's wrong, you point it out, it tries again, you fix the next thing. Prompt, answer, fix. Over and over. You end up being the quality control department for your own assistant.
A loop takes that job off your plate. Instead of you catching every mistake, you tell Claude what a good result looks like — and Claude checks its own work against that, fixes the weak parts itself, and only comes back to you once it genuinely can't make it better.
🧾 Prompting (the old way)
- You ask, Claude hands you a rough first draft
- You read it and spot the gaps
- You explain what's off, it tries again
- Repeat until you're worn out or settle
- You're the one doing all the checking
🔁 A loop (the new way)
- You tell Claude what "good" looks like
- It does the work, then grades its own output
- It fixes the weak parts on its own
- It repeats until nothing's worth fixing
- You get the polished version, not the first draft
The employee analogy
Picture two team members. One hands you a rough draft every single time and waits for you to mark it up in red pen. The other one does the work, re-reads it, catches their own mistakes, tidies the weak bits, and only brings it to you when it's genuinely ready. Same person, completely different amount of work for you. A loop turns Claude into the second one.
The Loop Prompt
This is the one that changes everything. Paste it over any task you'd normally give Claude — write this email, draft this proposal, build this spreadsheet — and it turns a one-shot answer into a self-checking loop. It works, then reviews its own output against the goal, lists what's weak, fixes it, and repeats. The cap of three rounds means it won't run forever, and it shows you a short summary of what changed each round so you can see it improving.
Here's the task: [DESCRIBE WHAT YOU WANT, AND WHAT A GREAT RESULT LOOKS LIKE]. Don't just give me a first draft. Work in a loop: 1. Do the task properly. 2. Then stop and review your own output against the goal above. Be honest — read it like someone who wants it to be great, not someone who wrote it. 3. List the specific parts that are weak, missing, unclear, or could be simpler. 4. Fix those weak parts. 5. Repeat steps 2–4 until a review pass finds nothing worth fixing. Rules: - Cap it at 3 rounds so you don't run forever. If it's still not perfect after 3, hand me what you have and tell me what's still not ideal. - After each round, show me a SHORT summary (2–4 lines) of what you changed and why, so I can see it improving. - When you're done, give me the final version clearly labelled as final.
The bit that makes it work
The magic line is "review your own output against the goal." Claude is genuinely good at spotting weak spots when you ask it to — it just doesn't do it unless you tell it to. Describe what "great" looks like at the top, and the loop has something real to grade itself against.
The Plan-Follow Prompt
Loops are powerful, which is exactly why you sometimes want Claude to stay on rails. When you've already worked out a plan — the steps, the order, the way you want it done — this prompt keeps Claude following that plan instead of getting a clever idea halfway through and wandering off. Build your plan first, then paste this to lock it in.
Here's the plan I want you to follow: [PASTE YOUR PLAN — the steps, in order.] Now work through it like this: - Follow the plan step by step, in order. Don't skip ahead. - Tick each step off as you finish it, so I can see where you're up to. - Do exactly what the step says — don't improvise, add extra steps, or change the approach without checking with me first. - If a step can't be done as written (something's missing, unclear, or won't work), STOP and flag it. Tell me what's blocking you and wait — don't guess or work around it. - When every step is ticked off, tell me it's done and give me a quick recap of what you finished.
When to use this one
Use the Loop Prompt when you want Claude to make something better than you could brief. Use the Plan-Follow Prompt when you already know exactly how you want it done and you just need it done, in order, without surprises. Two different jobs — keep both handy.
The Review Skill
This is the review step from the loop, pulled out on its own so you can point it at anything — an email you drafted, a page Claude built, a proposal, a spreadsheet. It grades the work like a picky customer, not a polite assistant, and hands you a short ranked list of what to fix. Paste it whenever you want a second opinion.
Review this output as a picky customer — someone who's paying for it and won't accept "good enough". Check three things: 1. Does it actually do what was asked? Point out anything it gets wrong or skips. 2. Is anything missing that should be there? 3. Is it more complicated than it needs to be? Where could it be simpler? Then give me the TOP 3 FIXES, ranked by impact — most important first. For each fix, one line: what's wrong and what to change. Be direct. I'd rather hear the honest version now than find it out later.
Save it as a skill so you never retype it
In Claude Code or Cowork, ask Claude to "save this review instruction as a skill called review." From then on you just say "run the review skill on this" and it does the whole check — no copy-pasting. That's the difference between a one-off prompt and a tool you actually reach for.
Run it on a schedule
Here's where it stops being a prompt and starts being a system. Once a loop does something useful — cleans up your inbox, drafts your weekly update, checks your numbers — you can have it run on its own, on a repeat. Set it once, and it happens every week without you lifting a finger.
How to set it up (the whole thing)
In Claude Code or Cowork, you don't need to touch any settings or write any code. You just ask. Say something like:
Claude handles the rest — it sets up the recurring task, remembers the loop you want run, and fires it on schedule. When Monday comes around, the work is already done and waiting for you.
The three steps, plainly
Start with one boring, repeating job
The best first loop to schedule is something you already do every week and secretly dread — the Monday numbers, the weekly client update, tidying your task list. Get that one running on a schedule and you'll feel the difference by the second week. Then add another.
One honest note
A scheduled loop still needs a check-in now and then. It's an assistant working while you're away, not a set-and-forget machine you never look at again. Skim the results occasionally so you'd catch it if something drifted — then trust it to do the boring part.
Ready to go deeper?
If three prompts can do this, imagine what AI can do for the rest of your business.
Wright Mode Membership
Join a community of women using AI to take real work off their plate. Live calls, copy-paste prompts and workflows, and ongoing support.
Claude Masterclass
Learn to use Claude like a pro — from prompting fundamentals to building real workflows that save hours every week.
Claude Code Masterclass
Go beyond the chat box. Build automations, process data and create tools with Claude Code — no developer experience needed.