retro

# retro ## Purpose Engineering retrospective engine. Analyzes git history, work patterns, and code quality signals to produce actionable retrospectives with per-person breakdowns, shipping streaks, and concrete improvement habits. Fills a gap in the Rune ecosystem — cook builds, review checks, but nothing reflects on HOW the team works. <HARD-GATE> Retro is READ-ONLY. It analyzes and reports — it does NOT modify code, create PRs, or change any files except its own output artifacts (.rune/retros/). Retro is ENCOURAGING but CANDID. Every critique is anchored in specific commits, not vague impressions. </HARD-GATE> ## Triggers - `/rune retro` — default 7-day retrospective - `/rune retro 24h` — daily standup review - `/rune retro 14d` — sprint retro (2 weeks) - `/rune retro 30d` — monthly review - `/rune retro compare` — current vs previous period side-by-side - `/rune retro --business` — cross-domain executive retrospective with HTML report (Business tier) - Called by `audit` (L2) for engineering health dimension - Auto-suggest: end of work week (Friday sessions) ## Calls (outbound) - `scout` (L2): scan codebase for test file counts, project structure - `plan` (L2): when retro identifies systemic bottlenecks — hand findings to plan for next sprint (e.g., "fix ratio >50% → allocate debugging time in next phase") - `journal` (L3): retro findings → ADR entries for recurring team patterns - `neural-memory` (L3): recall past retro insights for trend comparison; save this retro...