7 feedback loops for self-improving AI content workflows

You’re already giving your content material workflows suggestions. Each time you edit a draft, repair the identical awkward transition, or reword a obscure heading, you’re offering corrections that an iteration loop can seize, so the subsequent run begins nearer to what you’d approve.

I run these loops throughout articles, LinkedIn posts, video scripts, and touchdown web page copy. When an edit sample exhibits up 3 times throughout separate items, the system proposes an replace to its directions. I approve it, or I don’t. Both approach, I now not manually replace agent docs each time output drifts in the identical path.

Listed below are seven loops, from temporary growth via post-publish efficiency. I take advantage of Claude Code, however these buildings work in any agent framework. You don’t want all of them. In the event you’re constructing your first, begin with the standard gate (loop 3). In any other case, begin wherever your workflow retains breaking.

1. The upstream filter loop

Most iteration occurs after technology. This loop runs earlier than writing begins.

It’s value the additional step as a result of a weak angle is the most costly failure within the pipeline. By the point it reaches a completed draft, you’ve spent a full pipeline run plus your individual overview time discovering what a strategist agent might have advised you upfront. 

I run mine on angles I’m contemplating pitching to exterior publications, the place a killed angle prices nothing, and a foul pitch prices an editor’s belief.

The strategist agent evaluates the temporary or angle in opposition to outlined standards earlier than something is written and points certainly one of three verdicts:

• Move: Proceed to writing or pitching, relying on the workflow.
• Revise: One thing particular wants to vary first. The angle is just too near a chunk you’ve already revealed, the thesis is just too broad to help, the subject matches, however the viewers is unsuitable, or the argument wants a proof level you haven’t gathered but.
• Kill: The angle can’t be mounted with revision. There’s no unique standpoint, or the supply to help it doesn’t exist. The agent paperwork why, and the rationale is logged.

The kill log is the place this loop pays off. After sufficient runs, it exhibits which angle patterns constantly fail with out anybody reviewing particular person verdicts.

Earlier than you construct this, outline:

• Analysis standards: Authentic standpoint, thesis energy, and viewers match necessities.
• What triggers every verdict.
• The place verdicts and kill rationales get logged.

Dig deeper: How to build a Claude Code-powered second brain for agency work

2. The retrieval refinement loop

In a regular pipeline, a analysis agent retrieves sources, the author makes use of them, and issues floor on the finish when an editor flags claims that the sources don’t help. 

By then, the repair is dear: An editor can flag an unsourced declare, however can’t produce the lacking supply. This loop provides a checkpoint between analysis and writing.

In my article pipeline, the analysis agent retrieves sources for the deliberate piece. Earlier than the author runs, a mapping agent reads the define alongside these sources and asks one query per part: Does this proof help the claims this part must make? 

It scores every part’s sourcing energy on a 1-10 scale. For any part under your threshold, it writes the follow-up search queries itself as a result of it is aware of precisely what’s lacking. Solely then does the author run.

The distinction exhibits up within the draft. A author working from sources that don’t fairly help the deliberate claims produces hedges and generalizations. A author working from validated sources produces particular, defensible claims.

3. The standard gate with a revision cap

One-shotting content material produces AI slop. Including a top quality gate is the only repair. As a substitute of producing a chunk in the identical context window and calling it executed, a second agent opinions the draft in opposition to outlined standards, classifies what’s unsuitable, and sends it again to the author for revision. The author makes the corrections and returns the draft to the reviewer, who checks it once more.

Once I run this loop, I give every agent a clear context window and set a revision restrict. A draft that received’t go after two rounds has a structural or sourcing drawback that revision can’t repair.

The reviewer doesn’t should be one agent. I initially had my editor deal with fact-checking too, however combining the 2 jobs meant neither received executed nicely. So I break up them.

A devoted fact-checker now runs in its personal clear context window, takes the draft plus each supply it cites, and checks each to verify the draft precisely describes what the supply says, not simply that the hyperlink exists. Giving every agent a single job made each higher at it.

To construct your individual high quality gate, outline what every verdict means in your content material:

• Move: Each declare is sourced, the piece matches your voice information, and the construction serves the argument.
• Flag: Fixable points, like an undefined time period, a weak opening, or a declare that wants a stronger supply.
• Escalate: One thing revision can’t repair, like a skinny angle or lacking analysis.

Route something that hits the revision cap to a human as an alternative of letting it loop. As soon as the gate works, add express re-entry factors so you may drop a coworker’s draft instantly into the reviewer with out operating the complete workflow.

Dig deeper: How to turn Claude Code into your SEO command center

4. Rubric-based scoring and ensemble choice

A high quality gate tells you whether or not a draft handed. A scoring loop tells you why it didn’t and what would repair it.

Begin with a rubric that your agent will use to examine the content material. The standards depend upon what you’re creating and the purpose.

For instance, my LinkedIn put up rubric scores 10 standards, together with specificity and concreteness, unique standpoint, a single clear perception, and whether or not each line avoids platitudes.

I additionally constructed a rubric into an award submission analyzer utilizing the submission pointers. It’s been most helpful for evaluating submissions and pinpointing precisely what to strengthen in each.

Rating output in opposition to every criterion on an outlined scale, equivalent to 1-10. For each criterion under your threshold, have the scoring agent produce a particular prognosis as an alternative of a obscure judgment. Ship that data again to the author agent for revisions.

Embrace a revision cap. If a criterion received’t shut the hole after two rewrites, the issue is the angle or the analysis. A draft caught at a six on specificity after two revision cycles is lacking one thing that doesn’t exist within the supply materials. Scoring it once more received’t assist.

You can even use a rubric to guage a number of items. Generate a number of variations with completely different framings, then run a decide agent that compares them utilizing the rubric as a information. 

5. The adversarial problem loop

An adversarial agent builds the strongest doable case in opposition to a chunk of content material.

After a draft is produced, the adversarial agent assaults the thesis, the proof, and the logic connecting them. The output contains each objection it may possibly help with reasoning.

You’re not asking for “this declare is unsourced.” You’re asking for “right here is the strongest counterargument, right here is the proof for it, and right here is the place your logic doesn’t maintain.”

Share the output together with your author agent, which has to reply every objection: strengthen the piece or doc why the objection doesn’t change the argument.

This loop earns its carry on thought management and opinion items, the place the argument is the product. I run it by myself bylined articles earlier than anybody else sees them. How-tos and explainers don’t have a thesis to problem, so the standard gate is sufficient.

If a practitioner with completely different expertise might learn your draft and fairly disagree with its central declare, an adversarial agent will floor that disagreement earlier than your editor does.

Dig deeper: How a ‘client brain’ gives AI the context SEO work needs

6. The diff-and-learn loop

Each loop to this point improves the piece in entrance of it. This one improves the pipeline itself.

My article generator runs this loop. By the point a draft reaches me, it’s gone via a researcher, an outliner, a author, a number of editors, and a fact-checker. The workflow then saves two recordsdata: a Markdown model that stays frozen and a DOCX I edit and add to WordPress. As soon as the piece is revealed, a diff agent compares the frozen model with what I revealed, line by line.

For this to work, freeze the pipeline’s output earlier than you overview it, and by no means edit that file. Make your edits in a working copy. With out the frozen model, there’s no report of what the system produced and nothing to match your edits in opposition to.

When you’re executed enhancing, the diff agent classifies each distinction by sort:

• Language simplification.
• Tone shift.
• Structural reorder.
• Factual correction.
• Heading rewrite.

It retains a depend for every class. When a class reaches a threshold — for me, three or extra related fixes on one piece or throughout a number of — the loop proposes an replace to the directions for the pipeline stage accountable.

I approve or reject every proposal, and accredited guidelines apply robotically. Approving a rule the system caught earlier than I did is well my favourite second in any of those loops.

The brink is what makes this work: A repair that seems as soon as could also be particular to that piece, however three or extra appearances point out a sample value encoding.

Two guardrails hold this loop from going unsuitable. First, a human approves each proposed rule. Say you narrow a statistic from one piece as a result of it didn’t match that argument. With out an approval step, the system can flip that single edit right into a standing rule, equivalent to “keep away from statistics,” and apply it to every little thing that follows.

The opposite guardrail is a everlasting house for diff outcomes. In the event that they reset with every bit, the loop received’t discover that the identical repair confirmed up throughout 4 completely different articles, and that accumulation is the entire level.

The registry could be a spreadsheet, a JSON file, or a Markdown log. What issues is that it lives exterior any single session and persists throughout items. Have it observe:

• Per repair: Which piece, which class, what the pipeline produced, and what you modified it to.
• Per class: Complete depend, what number of separate items contributed, and whether or not the sample remains to be being watched or has already change into a rule.

Dig deeper: 6 content audit workflows to build in Claude

7. The performance-feedback loop

As soon as a chunk is revealed, search efficiency is the decision that counts. Most groups accumulate that verdict for reporting and cease. This loop places it to work: What search tells you about revealed items ought to change the briefs you write subsequent.

Arrange a scheduled routine or agent that pulls efficiency alerts weekly and flags items shifting in both path:

• Indicators: Rankings, click-through charge, impressions, and visitors, pulled via the Semrush MCP or API, or from Google Search Console through a BigQuery connector.
• Cadence: Weekly, so that you catch motion whereas there’s nonetheless time to reply.
• Flags: Items underperforming your individual related content material, rankings that by no means materialized, positions a chunk used to carry and misplaced, and items outperforming expectations. The winners matter as a lot because the losers as a result of they present you which ones choices to repeat.

A bit can go each inside gate and nonetheless fail in search. For every flagged piece, give an agent the unique temporary and the efficiency knowledge, and have it reply one query: Realizing how this piece carried out, what would you alter concerning the temporary?

A bit that by no means ranked, whereas related items did, often had an angle drawback: It entered a dialog the place you had nothing new to say. A bit rating for queries it by no means focused answered a distinct query than the one the temporary requested.

A warning as you set this up: Don’t learn a falling click-through charge alone as failure. AI solutions have pushed click-through charges down throughout search, so evaluate each bit in opposition to your individual related content material, not final 12 months’s benchmarks.

Then make the lesson everlasting. Add it to the strategist agent’s analysis standards and the kill log so the subsequent temporary begins with every little thing this piece simply taught you.

Construct for the failure mode you’re seeing

I created most of my loops as a result of I discovered myself making the identical corrections. In some unspecified time in the future, I began asking why the system wasn’t catching them. That query is often the temporary for the subsequent loop to construct.

If you end up continuously enhancing out the identical AI tells or asking Claude why it did one thing once more regardless of you telling it to not, take into account whether or not a suggestions loop might save a few of your sanity and enhance output.