PROJECT MANAGEMENT
PTO-Adjusted Capacity Recompute on Calendar Change
When team time-off changes on Google Calendar, recomputes the sprint's effective capacity against velocity-per-available-day and notifies the team in Microsoft Teams if…
How it runs
The automated pipeline, trigger to output.
- TriggerTime-off calendar change in Google CalendarGoogle Calendar
- ActionCompute remaining available person-days
- ActionRead current cycle commitment from LinearLinear
- LogicScale velocity to availability and compare
- OutputPost revised capacity to Microsoft TeamsMicrosoft Teams
What it does
This workflow keeps capacity honest when people take time off after planning. A change to the team's shared time-off calendar recalculates available person-days, scales the velocity baseline accordingly, and re-checks the active sprint, flagging it if the reduced capacity now falls short of the existing commitment.
When to use it
Use it when PTO and holidays routinely break sprint plans that were sized for full attendance. It re-runs the math automatically the moment availability shifts.
How it works
- 1A Google Calendar change event on the team time-off calendar triggers the run.
- 2The workflow computes remaining available person-days for the active sprint window.
- 3It reads the current cycle commitment from Linear.
- 4A logic step scales velocity to available days and compares against commitment.
- 5If now over-committed, it posts the revised capacity and shortfall to Microsoft Teams.
Set it up
What you configure once, before turning it on.
- 1Connect Google CalendarEvents, attendees, availability.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect Microsoft TeamsChannels, chats, files.
- 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.