What problem does it solve? Writing sprint or milestone retrospectives manually requires digging through plans, git logs, and old reports to reconstruct what actually happened, which is time-consuming and often produces vague, data-free summaries. ## Core Features & Use Cases - Plan vs. Actual Analysis: Compares sprint or milestone plans against git history to identify completed, modified, carried-over, and unplanned tasks. - Velocity and Debt Tracking: Computes completion rates, velocity trends across sprints, and TODO/FIXME/HACK counts to show whether technical debt is growing or shrinking. - Action Item Follow-Up: Checks whether previous retrospective action items were addressed and generates owned, deadline-bound action items for the next iteration. - Use Case: After finishing Sprint 7, invoke the skill to produce a structured retrospective with metrics tables, blocker analysis, and estimation accuracy, saved to production/sprints/sprint-7-retrospective.md. ## Quick Start Run the retrospective skill with the argument sprint-7 to generate a data-backed retrospective for the last sprint.