AI Coding Weekly

Pocock moves /retro into the main flow of his skills

The session retrospective graduates from prompt of the day to something he runs even when nothing went wrong.

Matt Pocock has added /retro into the "Main Flow" of his skills, which means the session retrospective is now a standing step in how he works rather than a one off suggestion. He says he considers it that important.

Matt Pocock
@mattpocockuk
X
Even running it on a 'successful' agent session can turn up inefficiencies and workarounds the agent is battling against.
Oct 5, 2026 · View on X

The prompt itself he posted earlier. It reads the last 10 coding agent sessions and looks for ways to make the repo easier to navigate, specifically hunting for places where agents take too long to find relevant information or rely on out of date docs. His framing then was that improving navigability is an underrated way to save tokens.

The part that justifies the promotion

The new argument is about when you run it. Pocock's case is not that /retro rescues bad sessions, it is that even a session you would call successful hides friction worth finding.

"Even running it on a 'successful' agent session can turn up inefficiencies and workarounds the agent is battling against," he wrote.

That is the difference between a debugging tool and a default step. If you only reach for a retro when an agent visibly fails, you only ever see the failures loud enough to notice. The workarounds an agent quietly routes around, a stale README, a module nobody can find from the entry point, a doc comment that contradicts the code, all land inside runs that look fine from the outside.

Why your own logs

For working engineers, the useful bit is where the evidence comes from. Session transcripts are a log of an unusually patient reader trying to understand your codebase, and they are specific to your repo rather than to any model. A retro over them points at what your project makes hard, not at what the model is bad at, and the fix is a file you can edit.

Pocock has been building on the same idea elsewhere in his skills. A separate prompt of his scans the last 25 sessions for skill invocations and then asks for recommendations on how a new release might improve his workflow. Same move, different window, your history as the input.

Have the good opinion, not the loud one

One email a day. Under three minutes. What working engineers found out about coding with AI.

Get the next one by email

Coding with AI, read daily so you do not have to. The experiments, the receipts and the arguments from engineers shipping real software. Not a changelog.