PROJECT MANAGEMENT
CEO-drafted sprint rescope briefing for overcommitted teams
On a manual or scheduled trigger, the CEO agent reads BigQuery velocity forecasts and Linear cycle plans, identifies overcommitted teams.
How it runs
The automated pipeline, trigger to output.
- TriggerManual or pre-planning trigger
- ActionRead forecasted capacity per teamBigQuery
- ActionPull committed cycle plans with prioritiesLinear
- LogicAgent selects deferral candidates per team
- OutputPublish rescope briefing to NotionNotion
What it does
This workflow produces a reasoned planning briefing, not just a threshold alert. The CEO agent reads the BigQuery velocity forecast snapshot and the committed plan for each Linear cycle, finds teams whose commitment outruns predicted capacity, and reasons about which issues to defer based on priority, dependencies, and estimate confidence. It writes a clear rescope recommendation per overcommitted team into a Notion page for the planning review.
When to use it
Use it ahead of a planning review when you want a judgment-based recommendation that weighs priority and risk, not a mechanical points-over-velocity flag. It turns raw capacity gaps into a defensible cut list.
How it works
- 1A manual or pre-planning schedule trigger starts the run.
- 2The agent reads forecasted capacity per team from BigQuery.
- 3It pulls each team's committed Linear cycle plan with priorities and estimates.
- 4It reasons over the gap to select deferral candidates per team.
- 5It composes a structured briefing and publishes it to Notion for review.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect LinearIssues, projects, cycles, triage.
- 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
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.
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.
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.
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…
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.