What problem does it solve? After finishing an epic, teams often skip structured reflection, losing lessons buried in story files and repeating the same mistakes in the next epic. This Skill runs a guided, no-blame retrospective that mines story records, checks follow-through on prior action items, and prepares the team for the next epic. ## Core Features & Use Cases - Epic Discovery and Verification: Detects the completed epic from sprint-status.yaml, verifies all stories are done, and warns before running a partial retrospective. - Deep Story Analysis: Reads every story file to extract dev notes, review feedback patterns, technical debt, 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, maps dependencies on completed work, and lists preparation gaps and technical prerequisites. - Use Case: After closing Epic 4 of a game project, ask for a retrospective; the Skill facilitates a multi-agent team discussion (Product Owner, Senior Dev, QA) with you as Project Lead, then produces a retrospective document with lessons learned and owned action items. ## Quick Start Ask the AI to run a retrospective for the epic we just finished.
