Write Linear Sprint Closeout Notes

The grind

Retro starts with note taking

Here's what doing this by hand looks like today, and why it doesn't scale.

• The team shipped a lot, but nobody remembers what, because the closeout always gets written in the first ten minutes of retro, badly.
• You list the merged PRs by hand from GitHub's interface.
• The Linear Done count does not match what actually shipped.
• Carryover items get forgotten until the next retro.

MewCP collapses all of this into one prompt. Here's what that looks like.

The flow

5 steps · 3 servers

Your agent runs it end-to-end

01

Pull the issues in the sprint with a status of Done.

LI

02

List the merged PRs in the sprint window.

03

Identify the carryover, meaning the in progress or blocked items.

LI

04

Surface two or three wins from the diff, like performance, polish, or reliability.

05

Drop the closeout into Notion under this sprint's folder.

The payoff

Retro talks outcomes, not inventory

The closeout is already on the page, so retro spends 30 minutes on what to change instead of ten on what happened.

Paste this into Claude, Codex, or any MCP-connected agent. It'll connect your apps and run the task from start to finish.

Run it yourself

Copy the prompt

Goal: Write Linear Sprint Closeout Notes

MCP servers needed (connected through MewCP): Linear, GitHub, Notion

Steps:
1. Pull the issues in the sprint with a status of Done.
2. List the merged PRs in the sprint window.
3. Identify the carryover, meaning the in progress or blocked items.
4. Surface two or three wins from the diff, like performance, polish, or reliability.
5. Drop the closeout into Notion under this sprint's folder.

Check with me before sending any message or changing data in a connected app.

More recipes

CLSE

Assemble Audit Evidence in Notion

Pull access reviews, export the WAF config, and assemble the evidence pack in Notion for the auditor walkthrough.