What problem does it solve? Engineering teams often lose track of what was actually shipped, who contributed what, and how code quality trends over time. This Skill automates the weekly retrospective by analyzing git commit history, work patterns, and code quality metrics, with persistent history so trends are visible across weeks. ## Core Features & Use Cases - Commit and Work Pattern Analysis: Reviews commit history and work patterns to summarize what the team shipped during the week or sprint. - Team-Aware Breakdowns: Breaks down per-person contributions with praise and growth areas for each team member. - Persistent Trend Tracking: Stores retrospective history so code quality metrics and output trends can be compared over time. - Use Case: At the end of a sprint, ask for a weekly retro to get a structured summary of shipped work, per-person contributions, and quality trends without manually digging through git logs. ## Quick Start Ask the agent to run a weekly retro analyzing what the team shipped this week with per-person contribution breakdowns.
