Log chats that go badly for later analysis

I use /retro to save agent sessions for later analysis.

I use this when a session goes badly, or otherwise leaves me with a sense of “hmm, we could improve this”.

The affordance is great because:

Fixing an issue immediately can easily derail a work session.
Sometimes you need several example sessions to make the pattern—and the fix—easy to see.¹
Punting with /retro means I know I’ll get to it later, if it matters. When I review the retro inbox, I rank the list, address the most important, and delete the rest.

My /week-review skill includes a “check the retro pile” step.

Footnotes

A recent example: Codex with GPT-5.6 Sol kept doing a wildly disproportionate amount of testing. A couple of /retro sessions made it much easier to identify and resolve the issue. ↩

I’m learning to work with AI, to help make AGI go well. This is my study journal.

Hide posts about coding

I use /retro to save agent sessions for later analysis.

I use this when a session goes badly, or otherwise leaves me with a sense of “hmm, we could improve this”.

The affordance is great because:

Fixing an issue immediately can easily derail a work session.
Sometimes you need several example sessions to make the pattern—and the fix—easy to see.¹
Punting with /retro means I know I’ll get to it later, if it matters. When I review the retro inbox, I rank the list, address the most important, and delete the rest.

My /week-review skill includes a “check the retro pile” step.

A recent example: Codex with GPT-5.6 Sol kept doing a wildly disproportionate amount of testing. A couple of /retro sessions made it much easier to identify and resolve the issue. ↩