What problem does it solve? After completing an epic, teams often skip structured reflection, losing valuable lessons from story records, review feedback, and technical debt. This Skill runs a guided, multi-agent retrospective that mines sprint-status files and story documents to surface patterns, verify follow-through on prior action items, and prepare for the next epic. ## Core Features & Use Cases - Epic Discovery & Verification: Detects the completed epic from sprint-status.yaml with priority fallback logic, and warns when stories are still pending before running a partial retro. - Deep Story Analysis: Reads every story file to extract dev notes, review feedback patterns, technical debt, testing insights, and velocity trends across the epic. - Continuity Tracking: Loads the previous epic's retrospective and cross-references action items and lessons to measure follow-through. - Next Epic Preparation: Previews the upcoming epic, maps dependencies on completed work, and identifies technical prerequisites and preparation gaps. - Use Case: After finishing Epic 3, say "run a retrospective" and the facilitator agent leads a blameless team discussion, then writes a retrospective document with action items and updates sprint-status. ## Quick Start Ask the assistant to run a retrospective on the epic you just completed, for example by saying "lets retro the epic 3".
