retrolisted

Find friction. Remove friction. Record what the rules actually caught. ## What to do Quickly scan what just happened — `git log --oneline -10` and any hook triggers you remember. Then output in this format: ``` RETRO — [date] Friction: - [what got in the way] → fix: [specific actionable change] Saves: - [rule/hook] caught [the specific real problem] — without it: [what would have shipped] Insights: - [something learned that should survive this session] Framework: - [cc-discipline improvement, if any — skip if none] ``` Rules: - **Only actionable friction** — Every friction item must have a "→ fix:" with a concrete change (adjust a threshold, add to CLAUDE.md, update memory, exempt a path). - **Only new** — Don't repeat friction that's already been addressed or recorded in memory. - **Be specific** — "streak-breaker was annoying" is not useful. "streak-breaker triggered 3x on config.yaml during template fill → fix: add config.yaml to docs/ exempt path, or raise config threshold to 10" is useful. - **Framework items are rare** — Most friction is project-specific. Only flag framework issues if the same problem would hit other projects too. - **Keep it short** — 3-5 items per section max. If you can't find friction, say "no friction found" and move on. An empty friction list is a good sign. Saves — read this before filling that section in: - **A save is not "what went well."** Log a save only when a rule or hook *changed the outcome*: it caught a real mistake, blocked a