What problem does it solve? Teams often skip structured reflection after completing an epic, losing valuable lessons from story records, code reviews, and technical debt that could improve future sprints. ## 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: Mines dev notes, review feedback, lessons learned, and technical debt sections across all story files to surface recurring patterns and breakthroughs. - Continuity Tracking: Cross-references the previous epic's retrospective action items against current execution to measure follow-through. - Next Epic Preparation: Previews the upcoming epic, identifies dependencies on completed work, and flags preparation gaps. - Use Case: After finishing Epic 3 of a product build, run the retrospective to generate a facilitated multi-agent discussion, a retrospective document with action items, and a readiness assessment for Epic 4. ## Quick Start Ask the agent to run a retrospective for the epic you just completed, for example by saying "run a retrospective" or "let's retro epic 3".
