PROJECT MANAGEMENT
Flag Linear tickets added after sprint lock and alert the team in Slack
Watches a locked Linear sprint cycle and, whenever a new issue is added to it after the lock timestamp, posts a scope-creep alert to Slack naming the ticket, its owner…
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue created or cycle-assignedLinear
- LogicAdded to a locked cycle after lock time?
- ActionFetch issue detail + cycle committed pointsLinear
- LogicCompute post-lock point delta vs committed plan
- OutputPost scope-creep alert to SlackSlack
What it does
This workflow treats your sprint lock as a contract. Once a Linear cycle is locked, any issue created in or moved into that cycle is detected as scope creep and surfaced to the team in real time, so additions are a deliberate decision rather than a silent drift.
When to use it
Run this when your team commits to a fixed sprint scope at planning and you want a tripwire for mid-sprint additions. Ideal for teams that practice sprint locking but still find velocity blown by untracked late entries.
How it works
- 1A Linear webhook fires when an issue is created or updated with a cycle assignment.
- 2A filter checks whether the issue's cycle is currently locked and whether the issue's added-to-cycle time is after the lock timestamp.
- 3If it passes, the workflow fetches the issue detail (title, assignee, estimate) and the cycle's committed point total from Linear.
- 4It computes the running point delta of post-lock additions versus the committed plan.
- 5A formatted alert is posted to the team's Slack channel naming the ticket, owner, estimate, and the new over-commit total.
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.