What problem does it solve? Teams often skip retrospectives or write vague ones because gathering sprint data, computing velocity, and tracking recurring blockers is tedious manual work. This Skill automates the analysis and produces a structured, data-backed retrospective document. ## Core Features & Use Cases - Automated Data Collection: Reads sprint plans, milestone definitions, sprint-status YAML, and git history to compare planned versus actual work. - Trend and Debt Analysis: Tracks velocity across sprints, counts TODO/FIXME/HACK comments, and follows up on previous action items. - Structured Output: Produces a markdown retrospective with metrics tables, blocker analysis, estimation accuracy, and prioritized action items saved to production/retrospectives/. - Use Case: After finishing sprint 4 of a game project, run the Skill to generate a retrospective showing a 75% completion rate, a growing TODO count, and three carryover tasks, then feed the action items directly into the next sprint plan. ## Quick Start Use the retrospective skill to generate a retrospective for sprint 4 and save it to production/retrospectives/.