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.
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.
Your agent runs it end-to-end.
- 01Pull issues in the sprint with status Done
- 02List merged PRs in the sprint window
- 03Identify carryover — in-progress or blocked items
- 04Surface 2–3 wins from the diff — perf, polish, reliability
- 05Drop 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.
Paste this into Claude, Cursor, or Codex. It'll install the CLI, connect your apps, and run the task — end to end.
Daily Morning Brief
One prompt pulls today's calendar, unread Gmail, open GitHub PRs, and overdue Notion tasks into a one-screen brief.
Read →Turn a Figma Flow Into a Spec and Tickets
Paste the Figma link. Your agent reads the screens, writes a one-page Notion spec, and files Linear tickets for each new screen — assigned, linked, and ready for planning.
Read →Draft Tomorrow's Sprint Planning Brief
Your agent pulls the Linear backlog and last week's PostHog funnel, recommends what to push to P0, and drops a one-page brief in Notion before planning starts.
Read →