What problem does it solve? After completing an epic, teams often skip structured reflection, losing valuable lessons from story implementation, code reviews, and technical debt. This Skill runs a guided, multi-agent retrospective that analyzes story records, checks follow-through on previous action items, and produces a documented retrospective with actionable improvements. ## Core Features & Use Cases - Automated Epic Discovery: Detects the completed epic from sprint-status.yaml with fallback to story file scanning and user confirmation. - Deep Story Analysis: Mines dev notes, review feedback, lessons learned, and technical debt sections across all stories to surface recurring patterns. - Continuity Tracking: Cross-references the previous epic's retrospective to verify whether committed action items were completed. - Next Epic Preparation: Previews the upcoming epic, identifies dependencies on completed work, and flags preparation gaps. - Use Case: After finishing Epic 3 of a game project, run the retrospective to generate a blameless lessons-learned document, verify Epic 2 action items were applied, and produce a readiness checklist for Epic 4. ## Quick Start Run a retrospective for the epic we just completed and generate the lessons-learned document.
