PROJECT MANAGEMENT
Daily Sprint Scope-Drift Digest to Notion
Each morning, compares the active Linear cycle's current scope against its day-one baseline and writes a dated drift report to a Notion database.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule (morning)
- ActionSnapshot active Linear cycle scopeLinear
- LogicDiff current scope against day-one baseline
- ActionAppend dated drift row to Notion logNotion
- OutputWrite summary title to Notion pageNotion
What it does
Once per day it snapshots the active Linear cycle, diffs it against the baseline captured on the sprint's first day, and appends a row to a Notion 'Sprint Drift Log' database: net issues added, points added, points removed, and the percentage change from the original commitment.
When to use it
Use it when retros keep stalling on 'why did we miss?' and nobody can reconstruct what got added mid-sprint. This gives the PM a durable, day-by-day paper trail of scope movement they can review at retro instead of arguing from memory.
How it works
- 1A daily schedule triggers each morning.
- 2An action step queries the active Linear cycle for all current issues and estimates.
- 3A logic step loads the stored baseline (the first snapshot of this cycle) and computes added, removed, and net-changed points.
- 4An action step appends a dated row to the Notion drift-log database with the deltas and links to newly added issues.
- 5The final output writes a one-line summary back to Notion as the page title for quick scanning.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect NotionPages, databases, comments.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.
CEO-Authored Weekly Cross-Team Dependency Risk Briefing
Weekly, the CEO agent gathers all tracked dependencies across Linear and ClickUp, reasons about which handoffs threaten upcoming milestones.
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.
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.
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.