An eval tells you which outputs are weak. The step Jeremy MacDonald called particularly clever is using that information to improve the work that produced them. In his BrightonSEO talk it was the third and last takeaway: create a feedback loop. (Part four of my series. Last time: build your first agentic eval with the RISE framework.)

How the loop works

The self-improving feedback loop A six-step cycle. One, generate with a RISE prompt. Two, evaluate each output against named criteria. Three, analyze the failures with a third prompt. Four, write the learnings as short lessons. Five, feed them back into the brief as constraints and examples to avoid. Six, run again from the better brief, which starts the loop over. 1 2 3 4 5 6 Generatewith a RISE prompt Evaluatescore against named criteria Analyze failureswhy did the low scorers fail? Write the learningspatterns, not single items Feed them backconstraints + examples to avoid Run againfrom a better brief The skill teaches itself
Jeremy MacDonald’s feedback loop from his BrightonSEO 2026 talk.
  1. Generate with a RISE prompt, for example keyword research from a brand PDF and product details.
  2. Evaluate each output with a second prompt that scores it against named criteria.
  3. Analyze the failures. A third prompt, with the role of an AI solution architect, reads the graded outputs and looks at the low scorers to understand why each one failed.
  4. Write the learnings. It produces a short set of lessons, such as which kinds of keywords keep scoring poorly on brand fit.
  5. Feed them back. Add the lessons to the original brief as constraints, and add the weak outputs as examples of what to avoid.
  6. Run again. The next generation starts from a better brief.

If you build this as a reusable skill, Jeremy said, it will learn and learn. Essentially, the skill teaches itself. His blunt view was that teams who aren’t working this way are falling behind.

What to put in the feedback

  • Patterns, not single items. “Keywords with competitor names score low on brand fit” is useful; one bad keyword isn’t.
  • Both sides of the scale. Include what scored highest so the brief reinforces good output.
  • Missing examples. If the analysis shows the original prompt had no examples of a case, add some. Jeremy noted that this is the stage where gaps in the examples show up.

Guardrails

These guardrails are my additions, not points Jeremy made. A self-improving loop can also drift. Don’t let it rewrite itself unattended:

  • Version your brief so you can roll back a change that made scores worse.
  • Keep a frozen test set of inputs you re-run after every change, to confirm that the score gains are real.
  • Review proposed changes before they go live, particularly anything that touches compliance or brand rules.
  • Watch for the eval being gamed: if scores climb while a human reviewer sees no improvement, the grader needs work. That’s the subject of the next post in this series.

This is also why I think senior people matter more, not less, as AI takes on more of the work: someone has to know when the loop is drifting.

Where to apply it

Jeremy’s examples went beyond keywords. The same pattern works for content briefs, support-ticket analysis and any multi-step process where each step can be checked. His former team used to finish work and hand it to him. A looped system checks every step on the way instead of only at the end.

Want help turning a one-off prompt into a workflow that improves itself? Get in touch.


Leave a Reply

Your email address will not be published. Required fields are marked *