What problem does it solve? After an epic finishes, no single coding session ever saw the whole change, so cross-story defects like god-class growth, duplication, and spec drift go unnoticed. This Skill reads the evidence an epic left behind — spec, story files, diffs, commits, sprint status — and produces a retrospective where every finding carries a source reference. ## Core Features & Use Cases - Evidence-based analysis: Derives per-story commit attribution and per-file change volume from git ranges, then builds aggregate views (architecture delta, duplication map, pattern divergence, spec reconciliation) across the full epic diff. - Acceptance verdict: Judges the epic against declared or profiled acceptance criteria and renders accepted, accepted-with-open-items, or rejected, with unfinished stories forcing a machine verdict of rejected. - Sprint-status integration: Updates sprint-status.yaml atomically via a comment-preserving script, marking the retro done and appending owned action items with stable IDs. - Use Case: After an unattended multi-story epic run, ask for a retrospective to get a document listing sourced findings, routed action items, follow-through on the previous epic's action items, and an acceptance decision an orchestrator can gate on. ## Quick Start Run a retrospective on epic 3 by saying "lets retro the epic 3" after its stories are marked done.
