AI Guides › Claude Mastery

The Weekly Review: Auditing What You Asked Claude To Do, And What It Actually Did

By Nigel Guy · 2 min read

Most people's relationship with Claude is entirely forward-looking — ask, get an answer, move to the next thing, never look back at last week's conversations unless something obviously broke. That means the same small mistakes and the same inefficient habits get repeated indefinitely, because nobody ever went back to check whether the pattern was working.

The rule: a short weekly look back at what you actually asked for, and what actually came back, catches drift that no single conversation will ever show you.

The mechanism: the weekly review

Once a week, spend ten minutes on four questions:

  1. What did I ask for repeatedly? If you typed a near-identical request three times, that's a template or a saved brief you haven't built yet — this week's repetition is next week's saved setup.
  2. Where did I have to correct it more than once? A single correction is normal. The same type of correction recurring across different conversations usually means your instructions are missing something structural, not that any one reply was unlucky.
  3. What did I accept without actually checking? Be honest here. If you can't now recall verifying something you used this week, that's the gap the next section of this library's habit guides is aimed at closing — note it, don't just feel bad about it.
  4. What worked well enough to reuse? A brief, a format, a phrasing that got a good result first time is worth saving somewhere you'll actually find it again, not just remembered vaguely as "that one time it worked."

What to skip

Skip trying to review every single conversation line by line — this is a pattern-spotting exercise across a week, not a transcript audit. And skip doing this daily; a week is usually the shortest interval where a genuine pattern (as opposed to one bad afternoon) becomes visible.

Guardrails

All 751 AI guides · JulieMango plans from £17/mo