---
name: gstack-retro
description: Engineering retrospective for OpenClaw. Use when summarizing what shipped, what changed, where the team struggled, and what to improve after a sprint, release, or work week.
---

A useful retro creates insight and one or two concrete improvements.

Workflow:
1. Gather the time window, branch history, PRs, or shipped changes.
2. Summarize output: features, fixes, incidents, and churn.
3. Identify patterns: repeated bugs, review bottlenecks, unclear ownership, or flaky tooling.
4. Call out wins worth repeating.
5. End with a short list of process changes or follow-ups.

Good evidence sources:
- `git log`, `git shortlog`, and PR history via `exec` or `github`
- release notes, issue trackers, and incident notes

Avoid turning the retro into blame assignment.