What problem does it solve? After completing a development epic, teams often skip structured reflection, losing valuable lessons and repeating mistakes. This Skill runs a guided, multi-agent retrospective that analyzes completed stories, reviews prior action items, and produces a documented retrospective with concrete improvement actions. ## Core Features & Use Cases - Epic Discovery & 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 surface recurring struggles, review feedback patterns, technical debt, and breakthrough moments across the epic. - Continuity Tracking: Cross-references the previous epic's retrospective to check whether committed action items were completed and lessons were applied. - Next Epic Preparation: Previews the upcoming epic, identifies dependencies on completed work, and flags preparation gaps and technical prerequisites. - Use Case: After finishing Epic 3 of a game project, ask the agent to run a retrospective; it facilitates a party-mode team discussion (Product Owner, Senior Dev, QA, Junior Dev), captures lessons, and writes an epic-3-retro document with action items. ## Quick Start Ask the agent to run a retrospective for the epic you just completed, for example: "run a retrospective for epic 3".
