Engineering Retrospective
Build a data-grounded engineering retrospective from git history: activity, hotspots, review patterns, and per-person growth notes for a given window.
How it runs
| # | Step | Who runs it | What happens |
|---|---|---|---|
| 1 | Define the retrospective window and evidence contract | Researcher | Lock the period, repositories, participants, questions, identity aliases, and privacy boundaries. |
| 2 | Collect and reconcile the engineering evidence | Researcher | Gather reproducible activity, churn, hotspot, collaboration, and quality signals with caveats. |
| 3 | Write the engineering retrospective | Developer | Turn the evidence into balanced lessons, growth notes, and owned experiments. |
| 4 | Evaluate the deliverable | Reviewer | Independently grade the observable deliverable and route it to finish, repair, or user escalation. |
| 5 | Repair the deliverable | Developer | Fix only the concrete gaps from the latest independent review. |
| 6 | Finish | Developer | All deterministic and reviewer criteria passed. |
| 7 | Escalate unresolved concerns | Developer | The bounded repair loop ended without a defensible pass. |
Say something like "weekly retro" or "what did we ship" or "engineering retrospective" in chat to start it.