1. What Is a Loop?#

In short: Loop Engineering means letting AI iterate continuously until it meets your quality standard.

It shifts the paradigm from “back-and-forth prompting” to “set the rules, let the AI loop until compliant”:

1
Manual Mode (You direct every step)           Loop Mode (You design the rules)
2
 You: Write auth module                       You: Set standards → Feed to AI
3
 AI: Created 9 files                          AI: Loops automatically:
4
 You: Token isn't persisted                    │  Generate → Validate → Non-compliant → Fix
5
 AI: Fixed, take a look                        │  Generate → Validate → Compliant → Stop
6
 You: Navigation is wrong                      │
7
 AI: Fixed again                               └→ You collect the result

The fundamental difference isn’t just about automation—it’s about where control resides:

• Manual Mode: control lives in every step of the turn-by-turn conversation.
• Loop Mode: control lives upfront, in the rules you design.

2. Concept Origin & Technical Background#

Loop Engineering is an engineering-focused synthesis of modern AI programming practices:

• Formally introduced by Addy Osmani in June 2026: as the former core lead of Chrome DevTools and currently the lead of Developer Experience for Google Cloud AI, Osmani argued that conversational AI programming shouldn’t rely on a single turn to get everything right at once. Instead, it requires clear success criteria and a “generate–validate–feedback” loop to iteratively converge on a correct result. He also noted that a model’s self-evaluation is inherently biased, which makes independent verification mechanisms essential.
• Validated in production by Boris Cherny (head of Claude Code): in an engineering talk, Cherny detailed how his team’s workflow shifted from turn-by-turn instruction prompting to a loop model. This model relies on verifiable termination conditions, independent reviewer roles, and state persistence—letting the agent complete the closed loop of generation, validation, and repair while human developers focus solely on initial rule design and final acceptance.

At its core, Loop Engineering shares the same philosophy as Test-Driven Development (TDD) and CI/CD pipelines: automating the repetitive cycle of generation, verification, and repair. It’s a proven production methodology developed by the creators of modern AI coding tools, not just a theoretical idea.

3. The Three Core Questions#

Designing a Loop comes down to answering three fundamental questions:

These seem simple, but almost every failing Loop stems from a lack of clarity on these three points. For example:

1
You: Evaluate this Skill for me.
2
AI: Evaluated! Looks great.
3
 → Problem: You said "looks great," but what does "great" actually mean?
4
    The AI is forced to judge its own work.

This leads to “false compliance”—the AI claims it met the standard, but it actually didn’t.

The core practice of Loop Engineering is turning subjective intuition into verifiable, deterministic rules. (We’ll dive deep into this in Part 2.)

4. A Pitfall You Should Know in Advance#

When I first tried a Loop, I made a mistake: I picked a domain I wasn’t familiar with as an example. When it came time to set the “evaluation standard,” I got completely stuck.

I realized: your evaluation standards are a direct reflection of your domain expertise. You can’t define “what passing looks like” if you don’t know what quality looks like in that field.

1
Unfamiliar Domain (e.g., deep system diagnostics):
2
  Someone asks: "What makes this documentation good?"
3
  → You don't know → You get stuck designing the standard.
4

5
Familiar Domain (e.g., tasks you perform daily):
6
  Someone asks: "What makes this feature complete?"
7
  → You can effortlessly list 5 key criteria → Design flows smoothly.

If you want to learn Loop Engineering, start with a domain you know inside and out. Your core professional expertise is the best sandbox for practicing Loops.

5. Key Takeaways#

1. A Loop lets AI iterate autonomously until standards are met, eliminating the need to micromanage every step.
2. Designing a Loop means answering three core questions: standard, feedback, and termination.
3. If these three questions are vague, your Loop will end up in “false compliance” or an endless idle loop.
4. Practice in a domain you know well—otherwise you won’t be able to define valid success standards.