PROJECT MANAGEMENT
Weekly velocity-drift stakeholder digest in Notion + email
Every Friday it pulls completed vs. committed work across the sprint, has an agent write a plain-English velocity-drift narrative, publishes it to a Notion page.
How it runs
The automated pipeline, trigger to output.
- TriggerFriday afternoon schedule
- ActionGather committed vs. completed scope and velocity trendLinear
- ActionAgent drafts velocity-drift narrative with risk calloutOpenAI
- ActionPublish dated digest to Notion stakeholder pageNotion
- OutputEmail digest to stakeholder listGmail
What it does
At the end of each sprint week it compares committed scope against completed scope, identifies the drift trend over recent sprints, and has an agent compose a stakeholder-readable narrative explaining what slipped, why it matters, and what's at risk next week. It saves the digest to Notion and emails it out.
When to use it
Use it when stakeholders want a clear weekly read on delivery health without reading the board. It turns raw velocity numbers into an honest, readable status that flags spillover risk before it becomes a surprise.
How it works
- 1A Friday afternoon schedule starts the run.
- 2It gathers committed and completed scope plus the rolling velocity trend from Linear.
- 3An agent analyzes the drift and drafts a narrative with a risk callout for next sprint.
- 4It creates a dated digest page in the Notion stakeholder workspace.
- 5It emails the same digest to the stakeholder distribution list via Gmail.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect NotionPages, databases, comments.
- 3Connect GmailRead, draft, send, label.
- 4Connect OpenAIModels, embeddings, files.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Project Management workflows
Zoom Sprint-Retro Audio to Themed Linear Action Board
Transcribes a recorded Zoom sprint retrospective, clusters the discussion into themes, and creates assigned Linear issues for each action item with the spoken owner attached.
Escalate Overdue Cross-Team Dependencies to Owners and Stakeholders
Each morning checks Linear for dependency-labeled issues past their due date and nudges the owner in Slack, escalating to the requesting team's lead if it stays unresolved.
Log every dependency slip to a Notion register and email the affected leads
On any Asana dependency slip, appends a structured row to a Notion blocker register and emails the leads of the downstream teams so there is both an auditable record and a direct…
Sprint-Retro Recap to Slack with Owner DMs
After a Zoom retro, posts a themed recap to the team Slack channel and direct-messages each owner the specific action items they committed to during the call.
Turn GitHub Blocking Comments into Tracked Cross-Team Promises
When a reviewer comments that a PR is blocked waiting on another team, the flow registers a tracked dependency in Linear and notifies the team that owes the unblock.
Scan Notion Meeting Notes for Action Items and Open ClickUp Dependency Tasks
On a schedule, parses recently edited Notion meeting-notes pages for action items that one team owes another and creates a ClickUp task for each, with due date and owner mapped.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.