Open the retro to a closeout doc that's already written
Walking into retro and want the numbers already on the page? Email Carly and she'll stitch Linear and GitHub into a Notion closeout — what shipped, what carried, and the wins worth calling out.
What Carly does
- 01 Pull issues in the sprint with status Done
- 02 List merged PRs in the sprint window
- 03 Identify carryover — in-progress or blocked items
- 04 Surface 2–3 wins from the diff — perf, polish, reliability
- 05 Drop the closeout in Notion under this sprint's folder
Retro talks outcomes, not inventory
The closeout is already on the page. Retro spends 30 minutes on what to change — not 10 on what happened.
Email this to Carly to kick it off.
Hey Carly, Retro is coming up — can you put together the sprint closeout? Pull all Linear issues in the sprint with status Done, and list the merged PRs from the sprint window so we have what actually shipped. Then call out the carryover — anything in-progress or blocked — and surface 2 or 3 wins worth highlighting from the diff (perf, polish, reliability — that kind of thing). Drop the whole thing in Notion under this sprint's folder. Leave it as a draft so I can give it a once-over before retro starts. Thanks!
More recipes for engineering teams
Cluster Sentry issues by root cause, match against Linear, and file the rest with stack + occurrence counts.
Read →First-pass review with correctness flags, missing-test calls, and a summary verdict — dropped straight into GitHub.
Read →Ack PagerDuty, pull the Datadog window, correlate deploys, start a war-room — so you land in the fix with context.
Read →Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
Get Carly Today →Or try our Free Group Scheduling Tool or Free Booking Page