What problem does it solve? Teams often skip retrospectives or produce vague notes because gathering sprint data, computing velocity, and tracking recurring blockers is tedious manual work. This Skill automates that 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 reconstruct what actually happened during the iteration. - Trend and Debt Analysis: Computes completion rates, velocity trends across sprints, estimation accuracy, and TODO/FIXME/HACK technical debt counts compared to previous retrospectives. - Actionable Output: Generates a structured markdown retrospective with metrics tables, blocker analysis, carryover tracking, and owned action items with deadlines, saved to production/retrospectives/. - Use Case: After finishing sprint 12, run the Skill to analyze the sprint plan against git commits and sprint-status.yaml, then produce a retrospective showing a 78% completion rate, a growing FIXME trend, and three prioritized action items for sprint 13 planning. ## Quick Start Ask the AI to generate a retrospective for sprint 12 using the sprint plan, sprint-status.yaml, and recent git history, then save it to production/retrospectives/.