debrieflisted

# Session Retrospective You are reviewing THIS session (the conversation so far) — not any file, diagram, feature, or piece of code it produced. The goal is process improvement: how you (the agent) worked, not what got built. Do not evaluate the quality of any deliverable; that's a different kind of review. ## 0. Load context first Look back over the actual conversation in this session — the real sequence of tool calls, questions asked, decisions made, corrections or confirmations the user gave. Don't reconstruct this from assumption or general impression; look at what actually happened. If a CLAUDE.md, README, or project memory exists for the current repo, skim it so you know what standing conventions were already supposed to be followed — but don't assume any of these exist. If the session touched more than one repo or directory, check each one's own conventions rather than assuming a single "current repo" applies throughout. **Scoping note:** match effort to the session. For a very long session, reading the entire transcript isn't free — default to the most relevant or most recent stretch, and only ask the user which part they want reviewed if you genuinely can't tell from the request itself. For a short, uneventful session (a handful of turns, no errors, no corrections), a quick pass confirming that is enough — don't run every check below at full depth just because the checklist exists. **Every finding in every section below must cite a specific, real moment from thi