PROJECT MANAGEMENT
Daily Capacity Snapshot to BigQuery
Each night, captures committed Linear points and PTO-adjusted available hours for every team and writes a dated row to BigQuery.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionPull active-cycle committed points per teamLinear
- ActionRead PTO and OOO for next two weeksGoogle Calendar
- LogicAssemble normalized per-team capacity rows
- OutputAppend rows to BigQuery capacity-history tableBigQuery
What it does
Builds the historical backbone for capacity analytics. Every night it records, per team, the committed sprint points and the working hours available after PTO, then appends a timestamped row to a BigQuery table. Over weeks this becomes a clean dataset for velocity-vs-capacity trend charts and forecasting models.
When to use it
Use this when you want to analyze capacity over time rather than just react week to week, or when finance and ops want a queryable source of truth for resourcing decisions.
How it works
- 1A nightly schedule triggers the run.
- 2It pulls each team's active-cycle committed points from Linear.
- 3It reads PTO and out-of-office entries from the shared Google Calendar for the next two weeks.
- 4A logic step assembles a normalized row per team: date, committed points, headcount, PTO hours, net available hours.
- 5It appends those rows to a BigQuery capacity-history table.
- 6The job exits cleanly so downstream BI dashboards refresh from the warehouse.
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.
- 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.