What problem does it solve? Engineering teams often lose track of what shipped each week and lack a structured way to review contributions, spot trends, and capture learnings. This Skill automates the weekly retrospective by analyzing commit history, work patterns, and code quality metrics with persistent history and trend tracking. ## Core Features & Use Cases - Automated retro generation: Analyzes commit history, work patterns, and code quality metrics to produce a weekly engineering retrospective. - Team-aware breakdowns: Breaks down per-person contributions with praise and growth areas for each team member. - Persistent history and trends: Loads prior retros, recent timeline events, and learnings from the local gstack project store to track trends over time. - Use Case: At the end of a sprint, ask for a weekly retro to get a summary of what shipped, per-person contribution highlights, and trend comparisons against previous retros. ## Quick Start Ask your agent to run the weekly retro to summarize what the team shipped this week with per-person contributions and trends.