Sprint Closeout Notes

For a tech lead who walks into retro wanting the numbers already on the page. One prompt stitches Linear and GitHub into a Notion closeout — what shipped, what carried, and the wins worth calling out.

Linear logoLinear
GitHub logoGitHub
Notion logoNotion
THE GRIND

Retro starts with note-taking

The team shipped a lot. Nobody remembers what because the closeout always gets written in the first 10 minutes of retro — badly.

Listing merged PRs by hand from GitHub's UI

Linear 'Done' count doesn't match what actually shipped

Carryover items get forgotten until the next retro

Composio collapses all of this into one prompt — here's what that looks like.

THE FLOW
5 steps · 3 toolkits

Your agent runs it end-to-end.

  1. 01
    Pull issues in the sprint with status Done
    linear logo
  2. 02
    List merged PRs in the sprint window
    github logo
  3. 03
    Identify carryover — in-progress or blocked items
    linear logo
  4. 04
    Surface 2–3 wins from the diff — perf, polish, reliability
  5. 05
    Drop the closeout in Notion under this sprint's folder
    notion logo
THE PAYOFF

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.

Paste this into Claude, Cursor, or Codex. It'll install the CLI, connect your apps, and run the task — end to end.