Send a weekly project status report
Assemble the week from Linear, GitHub and Slack into a report humans want to read.
Automated status reports remove the worst meeting on the calendar: the one where people read their task lists to each other. This workflow assembles the week from where the work actually happens (Linear, GitHub, Slack) and writes a status report a human wants to read: what shipped, what's moving, what's blocked, and what got decided.
What does this workflow do?
Every week the agent reads your Linear projects and cycles, merged GitHub work, and the decisions and discussions in your Slack channels. It writes a report structured for skimming: highlights first, then per-project status with real progress (issues closed against scope, not vibes), blockers with owners, and decisions made during the week with links.
The difference from a dashboard: the agent notices what the numbers don't say. A project with no movement for two weeks gets flagged. A blocker mentioned in a Slack thread but never filed gets surfaced. And the agent asks before it assumes: the project lead gets a one-line question ("Payments migration shows no movement. Blocked, or just not started?") before the report goes out.
How does it work?
- The agent gathers the week. Linear issues and cycles, GitHub merges and releases, decisions and blockers mentioned in Slack.
- It reconciles the picture. Cross-checking sources: work merged but not reflected in Linear, blockers discussed but not tracked, deadlines that quietly slipped.
- It asks before it assumes. Gaps and anomalies become quick questions to project owners. Answers take one tap and make the report accurate.
- It writes for readers. Highlights, per-project status, blockers with owners, decisions with links. Consistent format, so week-over-week comparison is easy.
- It posts and archives. To the Slack channel and a Notion archive. Leadership variants with less detail can go to a separate channel.
Who is this report for?
Founders and team leads who currently write it by hand on Friday afternoon, and teams whose standup has quietly become a status recital. The report replaces the assembly work, and the confirmation questions replace the "quick sync" that interrupts three people.
The workflow learns your team's shape: which projects matter to which audience, what your team means by blocked, which Slack channels carry signal. Formats and feedback persist, so the tenth report needs no correction.
Works with
Linear, GitHub, Slack, Notion, Google Docs. Runs weekly, or per sprint cycle.
Frequently asked questions
What sources feed the report?
Linear for issues, projects and cycles; GitHub for merged and released work; Slack for decisions and blockers discussed in channels. You pick the projects and channels in scope.
How does it avoid reporting stale or wrong status?
It cross-checks sources against each other and asks the project owner when something doesn't add up, before publishing. No silent guesses.
Can different audiences get different versions?
Yes. A detailed version for the team and a highlights version for leadership can run from the same data, each to its own channel or doc.
Does it replace standups?
It replaces the status-reading part. Teams keep standups for coordination and unblock discussions, which is what they were for.
Can I change the format?
Yes. Edit the template's report structure once and the workflow keeps it. Section-level feedback ("drop the commit counts") sticks from the next run.