PROJECT MANAGEMENT
GitHub PR throughput vs planned velocity reconciler
Weekly job that compares merged-PR delivery throughput from GitHub against the points a team committed in Linear.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionFetch merged PRs per teamGitHub
- ActionPull committed and completed cycle pointsLinear
- LogicCompute throughput vs plan divergence
- OutputPost estimation-health digest to SlackSlack
What it does
This workflow cross-checks two signals that should agree: planned story points and actual code shipped. Each week it pulls merged-PR counts and sizes per team from GitHub and the points committed and completed for the matching Linear cycle. It computes the divergence between planned velocity and real throughput, surfacing teams whose estimates are systematically inflated or deflated. The findings land in a Slack digest so estimation drift gets corrected.
When to use it
Use it when you suspect story-point estimates have drifted from reality and your velocity model is being fed bad inputs. Reconciling against shipped PRs keeps the forecaster honest.
How it works
- 1A weekly schedule triggers the reconciliation.
- 2The flow fetches merged PRs per team for the period from GitHub.
- 3It pulls committed and completed points for the matching Linear cycle.
- 4A logic step computes points-per-merged-PR divergence against the team baseline.
- 5Teams exceeding the drift threshold are compiled into a Slack estimation-health digest.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.