PROJECT MANAGEMENT
Weekly scope-creep digest grouping added points by stakeholder
Every Friday, totals the story points added to the active sprint after commit, groups them by originating stakeholder.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly Friday schedule
- ActionQuery Notion ledger for this cycle's additionsNotion
- LogicGroup added points by stakeholder and rank
- OutputPost ranked scope-creep digest to SlackSlack
What it does
Turns the running scope-creep ledger into a weekly leaderboard of pressure. It sums every point added after sprint commit, attributes each to its stakeholder, ranks who drove the most unplanned work, and broadcasts the summary.
When to use it
Use it for the standing Friday delivery review when you need a one-glance answer to "who kept changing scope this week and by how much?" Great for product and eng leads negotiating next sprint's capacity.
How it works
- 1A weekly schedule fires Friday morning.
- 2The flow queries the Notion scope-creep ledger for rows added during the current cycle.
- 3A grouping step aggregates total added points per stakeholder and computes the share of committed capacity consumed.
- 4It formats a ranked digest highlighting the top three drivers and any unattributed additions.
- 5The digest is posted to the delivery Slack channel with a deep link to the ledger as the output.
Set it up
What you configure once, before turning it on.
- 1Connect NotionPages, databases, comments.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.