retrolisted

# Retro — LLM-driven Session Retrospection One efficient LLM pass over a session (or the stored memory backlog) detects friction, classifies it into one of six destinations, and materializes approved learnings. **Core principle:** No silent writes — every materialization needs explicit per-proposal approval. ## Modes Detail per mode in `references/workflow.md`; full pipeline + commands in `commands/retro.md`. - **`/retro`** — Sweep: the whole current session. - **`/retro "<problem>"`** — Spotlight: one described issue. - **`/retro outcome [session-id|--since N]`** — replay a past session by what happened to its output (reverts, rejected PRs, follow-up fixes). - **`/retro audit [--scope project|repo|skill]`** — cross-session architectural drift, not per-session friction. - **`/retro promote`** — inventory already-written local memory (all slugs) and re-home each note upward (skill-update › project-rule › user-memory; never project-local memory), draining the source only after the upward write is verified. See `references/promote-mode.md`. - **Auto** — optional SessionEnd hook (`hooks/session-end.json`), off by default. ## Pipeline (all modes) 1. Mechanical pre-pass — `scripts/detect-mechanical.py` (Promote substitutes `scripts/scan-memory-inventory.py`). 2. LLM enrichment — add inferential signals; filter false positives. 3. Cross-session enrichment (optional) — Coach `events.sqlite` or JSONL scan. 4. Classify to one destination (`classification-heuristic.m