Weekly Engineering Retro
By snoozeButtonKing · Published · Updated
Turns a week of commits and incidents into a short retro: what shipped, what hurt, and the single change to try next week.
Tags: productivity, coding
Prompt template
## Weekly Engineering Retro Write this week's engineering retro from the evidence. - Week covered: [text: Date range] - Commit log or merged PRs: [textarea: Paste the list] - Incidents and alerts: [textarea: What broke and how long it lasted] - Goals set last week: [textarea: What the team planned] - Team mood or blockers: [textarea: Anything said in standup or chat] - Audience: [dropdown: Team only, Team and manager, Wider company] Group the commits into themes and write what shipped in plain language, tied to the goals set last week; say which goals were met, partly met, or missed. Next, list what hurt: incidents with their duration and cause, slow reviews, flaky tests, and work that was redone. Use numbers where the data has them, such as merged PRs, average review wait, and incident minutes. Name the most likely root cause behind the biggest pain rather than listing symptoms. Pick exactly one change for next week, with an owner and a way to tell whether it worked. Keep the whole retro under 400 words, blame no individual, and end with the goals proposed for next week.