gstack-openclaw-retro

Generate a weekly engineering retrospective by analyzing git workflow metrics to summarize team activity, attribute contributions per author, and surface growth signals. The retrospective produces a narrative reflecting shipped work and collaboration opportunities.

A team-aware engineering retrospective analyzes weekly engineering activity to attribute contributions to each member, identifying praise and growth areas. It provides role-aware guidance with per-person insights and actionable next steps for the engineering team.

Yes, you can track engineering metrics across multiple release cycles by storing persistent history in memory. This allows you to identify trends in commits, code quality, and velocity across consecutive weekly sprints.

Attribute code contributions during a sprint review by analyzing engineering activity data to generate per-author attribution. The retrospective summarizes individual contributions, highlighting specific praise and growth areas for each team member.

No, generating a retrospective satisfies data gathering and historical tracking requirements automatically. It analyzes engineering activity across all contributors within a specified 7-day window to produce an action-oriented summary without manual data collection.

Automated retrospectives focus on a default 7-day window and rely on engineering activity data for insights. They do not replace qualitative human feedback but instead provide persistent historical tracking and per-author attribution to support engineering reviews.