
Cross team status updates
Create an agent that pulls {{Linear}} updates, PR statuses, and release notes, then generates a weekly team update with per person task summaries, posting it to {{Slack}} and saving a full report as a {{Notion}} page.

Create an agent that pulls {{Linear}} updates, PR statuses, and release notes, then generates a weekly team update with per person task summaries, posting it to {{Slack}} and saving a full report as a {{Notion}} page.
Weekly status updates are one of those tasks that look simple but eat a lot of time. Product ops or team leads end up chasing updates across Linear, GitHub, and release notes, then rewriting the same information for Slack and Notion. Important work gets missed, updates are inconsistent, and the summary often depends on who spoke up last.
This agent removes that busywork by pulling the data straight from the source and producing a clear, consistent snapshot of what each person worked on, what shipped, and what is still in progress.
This is a perfect job for an agent because it is repetitive, cross tool, and rules driven. The agent can reliably read Linear changes, PR status, and release notes, map work to owners, and apply the same structure every week without bias or forgetting context. It does not replace human judgment, but it does automate the collection and formatting, so the team can focus on decisions and follow ups instead of writing updates.


.webp)
It pulls ownership and activity directly from Linear issues, linked PRs, and release notes, then groups updates by assignee and contributor.
It includes shipped work, in progress tasks, blocked items, and upcoming work, summarized per person and formatted for Slack and Notion.
Yes. You can control which fields are included, how detailed the summaries are, and whether the Slack version is short or more detailed.
No. It replaces manual status writing, not the conversations. The agent gives everyone the same baseline context so meetings focus on decisions, not updates.
.webp)
