PROJECT MANAGEMENT
Weekly Capacity Forecast: Sprint Commitments vs PTO
Every Monday, compares each team's committed Linear story points against available working hours after subtracting approved PTO.
How it runs
The automated pipeline, trigger to output.
- TriggerMonday 8am schedule
- ActionSum committed points per team from active Linear cycleLinear
- ActionPull PTO and holidays from shared Google CalendarGoogle Calendar
- LogicConvert points to hours and compare against available capacity
- LogicTag teams over vs under capacity
- OutputPost per-team load digest to SlackSlack
What it does
Produces a weekly snapshot of whether each team has bitten off more than it can chew. It pulls the points committed to the active Linear sprint, calculates real available hours from the shared Google Calendar (subtracting approved PTO and holidays), and flags teams that are over-allocated before the sprint goes sideways.
When to use it
Run this when you manage several squads and keep getting surprised mid-sprint by carryover. It turns "we thought we had the bandwidth" into a number you see every Monday morning.
How it works
- 1A Monday-morning schedule fires the run.
- 2It queries Linear for each team's active cycle and sums committed estimate points.
- 3It reads the shared Google Calendar for the sprint window and totals PTO and holiday hours per person.
- 4A logic step converts committed points to expected hours (using a per-team velocity ratio) and compares against available hours minus PTO.
- 5Teams exceeding their available hours are tagged over-capacity; the rest get a healthy/under tag.
- 6A formatted digest with each team's load percentage posts to a Slack planning channel.
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.