PROJECT MANAGEMENT
Sprint Start Overcommitment Guardrail
When a Linear cycle starts, checks committed points against PTO-adjusted capacity and, if a team is over-allocated, alerts the team lead in Slack and opens a Linear issue…
How it runs
The automated pipeline, trigger to output.
- TriggerLinear cycle started eventLinear
- ActionFetch committed points for new cycleLinear
- ActionRead approved PTO for cycle datesGoogle Calendar
- LogicCompute overcommit gap against threshold
- ActionDM team lead with gap and defer suggestionSlack
- OutputOpen Linear rebalance-scope issueLinear
What it does
Acts as a guardrail the moment a sprint begins. As soon as a Linear cycle starts, it checks whether the committed scope fits the hours the team actually has after PTO. If a team is overcommitted, it pings the lead and files a tracking issue so scope gets cut before work starts rather than after.
When to use it
Use this if teams routinely start sprints already underwater. Catching it on day one is far cheaper than discovering it at standup three days in.
How it works
- 1A Linear cycle-started event triggers the run.
- 2It fetches committed estimate points for the new cycle.
- 3It reads approved PTO from the shared Google Calendar for the cycle dates.
- 4A logic step computes the overcommit gap; if committed hours exceed available hours by a set threshold, it branches to the alert path.
- 5It DMs the team lead in Slack with the gap and the suggested points to defer.
- 6It opens a Linear issue titled "Rebalance sprint scope" assigned to the lead with the overage details.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect Google CalendarEvents, attendees, availability.
- 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.