Loop Engineering Reduced to Two Patterns

From Prompting to Loop Engineering

Prompting has been evolving in a clear direction.

First, there was human in the loop. The human stayed close to the model, reviewed outputs, corrected mistakes, and decided the next step. This gave control, but it also created many interruptions.

Then came goal-driven prompting. Instead of asking the model to do one small step at a time, we give it a clearer goal: what to achieve, what constraints to follow, and when to ask for help. The point is not to remove the human, but to reduce unnecessary interruptions.

The next stage is loop engineering. Instead of focusing only on the prompt, we design the cycle around it. The model takes an action, checks the result, updates what it knows, and tries again. This repeats until the goal is reached or something blocks progress.

Filter and Improve

At the most abstract level, there are only two loop patterns worth remembering: filter and improve.

A filter loop reduces many possibilities into a smaller set of stronger candidates.

It starts with a list, processes each item, evaluates the results, and keeps only the best ones. For example, a loop may collect many high-performing thumbnail examples, analyze each one, score their visual patterns, keep the top few, then use those patterns to generate and score new caption ideas.

In short: many items go in, only the strongest few come out.

An improve loop makes one thing good enough.

It starts with a current artifact, applies a change, verifies the result, and repeats until it passes. For example, a coding loop runs tests, reads the failure, edits the code, runs tests again, and continues until all tests pass. An SEO loop runs a speed test, optimizes the website, reruns the test, and repeats until the score is above 95.

In short: keep changing one thing until it passes.

Most practical loops are one of these two shapes, or a combination of both. A content workflow may filter many ideas down to a few strong candidates, then improve the best one until it meets a clear quality standard.

Loop engineering does not have to be complicated if you deconstruct your purpose into filter or improve.

To comment and continue discussing this article, please comment on the X Article.