What problem does it solve? Most retrospectives rely on feelings and memory, which miss what actually happened during a sprint or release. This Skill replaces subjective recollection with objective evidence by analyzing git history to compute concrete metrics and produce a structured retro report. ## Core Features & Use Cases - Git-Based Data Gathering: Sweeps commit history with git log, groups commits by author, and separates code churn from new capability. - Computed Retro Metrics: Calculates Shipping Streak, Focus Score, Complexity Delta, and Test Ratio using exact, reproducible git commands defined in the reference library. - Structured Report Generation: Writes a retro_YYYY_MM_DD.md report to docs/retros/ covering the big picture, objective metrics, highlights, growth opportunities, and the core velocity question. - Use Case: After a two-week sprint, run the retro to discover that a low Focus Score reveals hidden context-switching drag, then extract action items into the planning queue. ## Quick Start Ask the agent to run a retrospective for the last 7 days so it sweeps git history, computes the retro metrics, and writes a structured report to docs/retros/.
