PROJECT MANAGEMENT
Daily audit of post-lock Jira-style sprint additions to a Notion changelog
Runs each morning, diffs the current Linear sprint backlog against the snapshot taken at lock.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekday morning schedule
- ActionPull active cycle's current issuesLinear
- LogicDiff against locked snapshot for net-new tickets
- ActionAppend additions to Notion scope-change logNotion
- OutputSend PM daily creep digestSlack
What it does
Produces a daily, auditable record of scope changes on the in-flight sprint. It compares today's cycle contents against the locked-at-planning snapshot, identifies every ticket added since, appends each to a Notion changelog page, and sends the PM a single digest of the day's creep with the cumulative point total.
When to use it
Use this when you need a paper trail for retro and stakeholder reporting — not a real-time gate, but a once-a-day reconciliation that answers "what got added to this sprint and by whom."
How it works
- 1A scheduled trigger runs every weekday morning.
- 2An action pulls the active Linear cycle's current issue set.
- 3A logic step diffs it against the stored lock snapshot to isolate net-new tickets.
- 4An action appends each new ticket, requester, and estimate as rows in a Notion scope-change log with a running point total.
- 5A Slack digest summarizes the day's additions and cumulative overage to the PM.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect NotionPages, databases, comments.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.