What problem does it solve? Writing a weekly engineering retrospective means digging through git logs, remembering what shipped, and tracking team contributions by hand. This Skill automates that analysis and keeps a persistent history so trends are visible across weeks. ## Core Features & Use Cases - Commit and Work Pattern Analysis: Reviews commit history and code quality metrics 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 History and Trends: Stores prior retros, timeline events, and learnings per project so each new retrospective can compare against past weeks. - Use Case: At the end of a sprint, ask for a weekly retro and receive a structured report covering shipped work, individual contributions, and trends versus previous retros. ## Quick Start Ask the assistant to run a weekly retro for this repository to analyze the recent commit history and produce a team retrospective report.