PROJECT MANAGEMENT
Daily reconcile of the live Linear sprint against the locked Notion plan
Each morning compares the current Linear cycle's issues against the committed scope recorded in a Notion sprint plan, then updates the Notion page with a table of added, removed…
How it runs
The automated pipeline, trigger to output.
- TriggerWeekday morning schedule
- ActionRead committed scope from Notion planNotion
- ActionPull current cycle issues from LinearLinear
- LogicDiff and classify added/dropped/re-estimated
- OutputWrite reconciliation table back to NotionNotion
What it does
This workflow keeps your written sprint plan honest. The committed scope lives in a Notion sprint page; the live work lives in Linear. Every morning it diffs the two and writes the variance back into Notion so anyone reading the plan sees exactly what drifted.
When to use it
Use it when planning artifacts and the issue tracker diverge over a sprint and you want a single source of truth that reflects reality. Good for leads who report sprint health to stakeholders from a Notion doc.
How it works
- 1A scheduled trigger runs each weekday morning.
- 2The workflow reads the committed issue list and point total from the locked Notion sprint plan.
- 3It pulls the current cycle's issues and estimates from Linear.
- 4A diff step classifies each issue as committed, added-after-lock, dropped, or re-estimated, and computes a creep percentage.
- 5The Notion sprint page is updated with a reconciliation table and the creep figure, and the page's status property is set to flag if creep exceeds a threshold.
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.