PROJECT MANAGEMENT
Weekly Multi-Team Scope-Creep Leaderboard
Every week, aggregates mid-sprint additions across all active Linear cycles and posts a ranked leaderboard to Slack showing which teams are adding the most unplanned work.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionEnumerate all active cycles across teamsLinear
- LogicCompute added-after-start points and rank teams
- ActionArchive per-team breakdown in NotionNotion
- OutputPost leaderboard to leadership SlackSlack
What it does
Once a week this workflow scans every active Linear cycle, counts the points and issues added after each cycle's start, and ranks teams from most to least scope creep. It posts a digestible leaderboard to a leadership Slack channel and archives the detailed per-team breakdown in Notion for trend tracking.
When to use it
Use it at the program or org level when you manage multiple squads and want to spot systemic scope-creep patterns rather than one-off incidents. It surfaces which teams consistently overcommit or absorb unplanned work so process fixes can be targeted.
How it works
- 1A weekly schedule triggers the run.
- 2An action enumerates all active Linear cycles across teams and pulls their issues and start dates.
- 3A logic step computes added-after-start points per team and sorts them into a ranking.
- 4An action writes the full per-team breakdown to a Notion report page.
- 5The output posts the ranked top offenders and org-wide totals to the leadership Slack channel with a link to the Notion detail.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect NotionPages, databases, comments.
- 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.