retrolisted

# Retro ## Core Rule A retrospective answers four questions over a window of time: **what shipped, what keeps going wrong, what was learned, and what is still open.** It is *process* reflection — the narrative `/scorecard`'s numbers cannot give you. Where scorecard says "citation-gate failed 14 times," retro says "the failures cluster in the Discussion, where I keep drafting claims before the source is in `references.bib` — that is the same root cause Reviewer 2 flagged twice; encode it as a Top Rule." The retro's most valuable output is the **recurring-critique scan**: the patterns to fix, ranked by how often a reviewer has hit them. A one-off critique is a fix; a *recurring* one is a rule (`CLAUDE.md → Self-Improvement Loop`). Retro is how those rules get surfaced and promoted. It is honest, not flattering — a retro that lists only wins is broken. ## When to Use Invoke with `/retro` when: - Closing out a working week or a manuscript milestone (a section finished, a draft sent to a co-author, a revision returned). - After a `/scorecard` shows a trend you want to *understand and act on*, not just observe. - Before a heavy revision push — to load the recurring reviewer critiques into context so you do not re-make the same mistakes in the new prose. - Whenever the same correction has come back more than once and you want it encoded as a rule rather than re-explained. Scope the window with an argument: `/retro` defaults to the last 7 days; `/retro 14` or `/retro since 202