Does this work with any Linear plan?

Yes. As long as your Linear account can read issues for the teams you care about, the agent can pull what it needs.

What if my team uses GitHub Enterprise or private repos?

That is fine. The agent uses your own GitHub login, so it can read whichever repos you already have access to.

How does it decide what slipped?

Anything that opened but did not close in the seven day window, plus pull requests sitting in review longer than 3 days. You can change the threshold.

Can it post the TL;DR to more than one Slack channel?

Yes. You can send it to multiple channels at once, or swap Slack for an email recipient if you prefer.

Will it expose sensitive details from issues or PRs?

It only summarizes what is already in your issue descriptions and PR titles. Scope the retro to specific Linear teams or repos to keep it focused on what your team should see.

Weekly Engineering Retrospective: Linear + GitHub Auto-Drafted

Every Friday at 5pm, run an agent that drafts an internal engineering retrospective for my team. Trigger is cron, weekly on Friday at 5pm.

Step one: pull the last seven days of work. From Linear, use List Issues to get every issue that was completed, started, or moved into a blocked state in that window. From GitHub, use List Pull Requests and Search Issues and Pull Requests to pull every PR merged into the main branches of our key repos this week, plus PRs that opened in the window and are still in review.

Step two: use AI Generation (chat-completion) to synthesize a structured retro with four sections: what shipped (grouped by team or project), what slipped (Linear issues that opened but did not close in the window, plus PRs sitting in review longer than 3 days), recurring themes or blockers across issue descriptions and PR titles, and two or three suggestions for the next cycle.

Step three: file the full retro as a new page in our Notion engineering retros database using Notion Create a Page. Title it with the week ending date. Inside the page, include direct links back to the source Linear issues and pull requests so anyone reading can click through.

Step four: send a tight five-bullet TL;DR with the Notion page link to our #engineering Slack channel using Slack Send a Message.

Tone is factual, no marketing fluff. Do not use em dashes anywhere in the output. Use periods or commas instead.

What it does

Pulls this week's Linear issues that were completed, started, or moved into blocked alongside the pull requests merged into your main branches
Drafts a structured retro covering what shipped, what slipped, recurring themes, and two or three suggestions for next cycle
Files the full retro as a new page in your Notion engineering retros database with direct links back to every source issue and PR
Sends a tight five-bullet TL;DR with the Notion link to your engineering Slack channel so the whole team sees it

What you’ll need

A Linear workspace where your team tracks issues
A GitHub account with access to your main repos
A Notion workspace with a database set up for engineering retros
A Slack workspace where the agent can post in your engineering channel

How to customize it

Move the run time. Friday at 5pm is the default, but Thursday end of day or Monday morning work too
Choose which GitHub repos count as your main repos and which Linear teams or projects to scope the retro to
Tune what counts as slipped. The default flags PRs sitting in review longer than 3 days, and you can raise or lower that threshold
Swap the Slack channel, or fan the TL;DR out to multiple channels

Use cases

AI Reports
Daily Digests

Weekly engineering retrospective from Linear and GitHub

Integrations

Type

Categories

What it does

What you’ll need

How to customize it

Use cases

FAQs

Related prompts