PROJECT MANAGEMENT
Flag tickets added to a locked Linear sprint and estimate impact
Watches a locked Linear cycle for issues added after the lock timestamp, sums their point estimate against remaining capacity.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue added or updated in active cycleLinear
- LogicKeep only issues added after cycle lock time
- ActionFetch cycle committed, done, and remaining capacityLinear
- LogicCompute projected scope overage percentage
- OutputPost PM sign-off request with Approve/RejectSlack
What it does
Detects scope creep on an in-flight Linear cycle. When a new issue is moved into a cycle that has already been locked, it calculates how many points were added versus the team's remaining capacity and asks the PM to approve or reject the addition before work proceeds.
When to use it
Run this when your team commits to a fixed cycle scope at sprint planning and you want a hard gate on mid-sprint additions — no silent slipping of new tickets into a sealed plan.
How it works
- 1A Linear webhook fires when an issue is assigned to or updated within the active cycle.
- 2A logic step compares the issue's `addedToCycleAt` against the cycle's stored lock time; non-post-lock changes are dropped.
- 3An action queries Linear for the cycle's committed points, completed points, and remaining days to derive current capacity.
- 4A logic step computes the projected overage percentage from the new issue's estimate.
- 5A Slack message goes to the PM with the ticket, the overage, and Approve / Reject buttons recorded back as a Linear label.
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.