Retro — LLM-driven Session Retrospection

This skill replaces continuous friction-detection hooks with a single efficient LLM pass over the session transcript. It detects friction, classifies into one of six destinations, and materializes approved learnings.

Core principle: No silent writes. Every materialization requires explicit user approval per proposal.

Modes

/retro — Sweep

Analyze the entire current session. Returns ≤10 actionable proposals grouped by destination. Use at session end or when you sense friction accumulated.

/retro "<problem>" — Spotlight

Focus on a specific issue described in the argument. Returns proposals only for that issue. Use mid-session for direct fixes (e.g. "the assistant kept forgetting we use bun, not npm").

/retro outcome [session-id|--since N] — Outcome (Schicht D)

Replay a past session through the lens of what happened to its output afterwards. Detects: commits reverted, PRs rejected, CI failures, follow-up sessions fixing earlier work, issues filed referencing session files. Use periodically (e.g. monthly) or when you suspect a past decision was wrong.

/retro audit [--scope project|repo|skill] — Constitutional audit

Cross-session architectural review with a longer horizon (weeks/months). Detects design drift, convention erosion, and patterns that don't manifest as per-session friction but accumulate over time. Same skill, broader window. Use when you want a "is the system on track?" health check, not a "what went wrong this session?" view.