PROJECT MANAGEMENT
Linear sprint capacity guard against rolling velocity
When a Linear cycle starts, sums the committed story points and compares them to the team's rolling 3-cycle average velocity, posting a Slack warning if the plan is overcommitted.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear cycle startedLinear
- ActionSum committed story points in cycleLinear
- ActionFetch last 3 cycles' completed pointsLinear
- LogicCommitment exceeds rolling velocity + buffer?
- OutputPost overcommitment warning to SlackSlack
What it does
This workflow watches Linear for the start of a new cycle, then checks whether the team has bitten off more than its recent history says it can chew. It pulls the total estimate of every issue assigned to the new cycle and compares that against the average completed points across the last three cycles. If the commitment exceeds rolling velocity by a configurable margin, it raises a clear, actionable alert in Slack so the team can rescope before work begins.
When to use it
Use it when your team plans in Linear cycles and repeatedly carries unfinished work into the next sprint. It catches overcommitment on day one instead of at the mid-sprint check-in, giving leads time to defer scope while it is still cheap.
How it works
- 1A Linear webhook fires when a new cycle becomes active.
- 2The flow fetches all issues in the cycle and sums their estimates.
- 3It queries the last three completed cycles and computes average delivered points.
- 4A logic step compares committed points to velocity plus the buffer margin.
- 5If over the threshold, a Slack message names the team, the gap, and the suggested issues to cut.
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
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.
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.
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.
Log every dependency slip to a Notion register and email the affected leads
On any Asana dependency slip, appends a structured row to a Notion blocker register and emails the leads of the downstream teams so there is both an auditable record and a direct…
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.