PROJECT MANAGEMENT
Sprint Over-Commitment Guard from Velocity Baseline
When a new sprint is locked in Linear, compares committed story points against the team's trailing velocity and posts a Slack warning if the sprint is over-committed beyond…
How it runs
The automated pipeline, trigger to output.
- TriggerLinear cycle startsLinear
- ActionFetch committed issues and sum estimatesLinear
- ActionPull last N completed cycles for velocity averageLinear
- LogicCompare commitment vs. velocity + buffer
- OutputPost over-commitment warning to SlackSlack
What it does
At the moment a Linear cycle starts, this workflow sums the committed story points and weighs them against your team's recent delivery history. If the commitment exceeds a configurable buffer over the rolling average, it raises a flag in Slack before the team is mid-sprint and already behind.
When to use it
Run this when your team plans in Linear cycles and routinely finishes sprints red because planning ignores real throughput. It catches over-commitment at lock-in, when scope can still be trimmed.
How it works
- 1A Linear cycle-start event fires the workflow.
- 2The workflow pulls committed issues for the new cycle and totals their estimates.
- 3It queries the last several completed cycles to compute a trailing velocity average and standard deviation.
- 4A logic step compares commitment against average plus the allowed buffer.
- 5If over-committed, it posts a Slack alert to the team channel naming the overage, the baseline, and the issues pushing it over.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.