What problem does it solve?
It turns scattered commit activity into a clear weekly engineering retrospective, including per-person contribution breakdowns and trend-aware quality metrics, so teams stop guessing and start improving with consistent signals.
Core Features & Use Cases
- Weekly retro from shipping evidence: Synthesizes commit history and work patterns into a structured retrospective narrative aligned to team outcomes, not just a changelog; use it at the end of each week or sprint when asked for “weekly retro” or “what did we ship”.
- Persistent history and trend tracking: Loads prior retros and a recent timeline/learnings context from gstack project artifacts to summarize what improved, what regressed, and what to focus on next.
- Team-aware feedback with actionable growth areas: Breaks down per-person contributions, provides praise, and identifies growth opportunities while keeping the output focused on engineering quality and delivery.
Quick Start
Ask for the weekly retrospective by saying: weekly retro for this project.