retrolisted

# Retro The only loop through which Tyran gets better at *this* repo instead of repeating the same mistake every initiative. **You normally do not have to invoke this.** The `Stop` gate refuses one turn when an initiative has all its tickets merged and no retrospective recorded since the last merge. This skill is what you run when it does — or when you want one early. ## 1. Spawn the retrospector Spawn `tyran:retro` at the tier `node "${CLAUDE_PLUGIN_ROOT}/scripts/tiers.mjs" --role retro` resolves, over the initiative's `PLAN.md`, `NOTES.md`, the agents' reports, and the initiative's git log. Do not do this work yourself in the conducting session. The retrospector's value comes from reading the record cold; a conductor reviewing its own initiative rates its own decisions, and rates them well. ## 2. Record the outcome — including "nothing" Every retro ends with a journal entry, whatever it concluded: ```bash node "${CLAUDE_PLUGIN_ROOT}/scripts/journal.mjs" append "$J" retro.entry "$INIT" \ --actor retro --data '{"kind":"skill","target":"skills/run/SKILL.md","confidence":"medium"}' ``` `kind` is `skill`, `agent`, `script`, `doc`, `knowledge` — or **`skipped`** with the reason, when the judgement is that this initiative has nothing worth changing. That is a correct outcome and it settles the gate exactly like any other. A retro that always finds something is not learning, it is padding. **When `kind` is `skill`, follow `skill-writing`.** New skills are AUTO class — y