PROJECT MANAGEMENT
Cross-Team Capacity Rebalance Advisor
On request, an agent reviews every team's committed Linear load against PTO-adjusted capacity and BigQuery velocity history.
How it runs
The automated pipeline, trigger to output.
- TriggerManual on-demand run
- ActionGather committed points and assignees per teamLinear
- ActionRead PTO and holidays for planning windowGoogle Calendar
- ActionQuery recent velocity history per teamBigQuery
- LogicReason over load, capacity, and history to find imbalances
- OutputPost rebalancing plan with rationale to SlackSlack
What it does
Gives a planning lead an analyst-grade rebalancing recommendation across all squads. An agent reads each team's committed Linear scope, subtracts PTO from the shared calendar, pulls recent velocity trends from BigQuery, and reasons about where slack and strain exist. It then drafts a concrete plan: which teams are overloaded, which have headroom, and specific work it suggests moving.
When to use it
Use this before a planning meeting when you need more than a red/green flag. It is for the judgment call of who should help whom, grounded in real commitments, time off, and historical throughput.
How it works
- 1A manual run kicks off the agent on demand.
- 2The agent gathers committed points and assignees per team from Linear.
- 3It reads PTO and holidays from the shared Google Calendar for the planning window.
- 4It queries BigQuery for each team's recent velocity to calibrate realistic throughput.
- 5The agent reasons over load, capacity, and history to identify imbalances and candidate work to move.
- 6It posts a written rebalancing plan with rationale to a Slack planning channel for the lead to approve.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect Google CalendarEvents, attendees, availability.
- 3Connect BigQueryDatasets, queries, schemas.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.
Log every dependency slip to a Notion register and email the affected leads
On any Asana dependency slip, appends a structured row to a Notion blocker register and emails the leads of the downstream teams so there is both an auditable record and a direct…
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.
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.
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.