What problem does it solve? After completing an epic, teams often skip structured reflection, losing valuable lessons about what worked, what failed, and what to improve. This Skill runs a guided, multi-agent retrospective that analyzes story records, checks follow-through on previous action items, and produces actionable insights for the next epic. ## Core Features & Use Cases - Epic Discovery and Verification: Automatically detects the completed epic from sprint-status.yaml, verifies story completion, and warns when running a retrospective on an incomplete epic. - Deep Story Analysis: Reads every story file to extract dev notes, review feedback patterns, technical debt, testing insights, and recurring struggles across the epic. - Continuity Tracking: Loads the previous epic's retrospective and scores each prior action item as completed, in progress, or not addressed. - Next Epic Preparation: Previews the upcoming epic, identifies dependencies on completed work, and lists technical prerequisites and preparation gaps. - Use Case: After finishing Epic 3 of a game project, ask for a retrospective. The Skill facilitates a blame-free team discussion with agents (Product Owner, Senior Dev, QA, Junior Dev), surfaces patterns like recurring code review feedback, and outputs a retrospective document with action items. ## Quick Start Run a retrospective for the epic we just completed and extract lessons learned for the next one.
