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, ending in an honest acceptance verdict. ## Core Features & Use Cases - Evidence-based analysis: Gathers the epic spec, story files, diff range, and per-story commits via deterministic scripts, then derives aggregate views (architecture delta, duplication map, god-class growth, spec reconciliation) that no single diff hunk reveals. - Acceptance verdict with fail-safes: Judges the epic against declared or profiled acceptance criteria as accepted, accepted-with-open-items, or rejected; unfinished stories force a machine verdict of rejected unless a human overrides. - Sprint-status integration: Updates sprint-status.yaml atomically through a comment-preserving script that marks the retro done, appends owned action items, and validates every write with rollback on failure. - 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 a verdict an orchestrator can gate the next epic on. ## Quick Start Ask the assistant to run a retrospective on the epic you just finished, for example by saying "run a retrospective on epic 3".
