PROJECT MANAGEMENT
Real-time alert when a new issue pushes an epic past its creep threshold
Fires the moment an issue is added to a Linear epic, recomputes the epic's total points against the kickoff baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerIssue added to a Linear epicLinear
- LogicConfirm parent is a tracked epic with a baseline
- ActionFetch epic's current total points from LinearLinear
- LogicCompute growth and check threshold breach
- OutputAlert the lead in Microsoft Teams with the triggering issueMicrosoft Teams
What it does
Catches scope creep at the instant it happens instead of on a daily sweep. Whenever an issue is created in or moved into an epic, it recalculates the epic's total points, compares against the stored kickoff baseline, and if that single addition crosses your growth threshold it sends an immediate alert to the lead in Microsoft Teams, naming the issue that caused the breach.
When to use it
Use it on high-stakes epics with firm commitments where you want to challenge each scope addition in real time, not discover the accumulation a week later. Complements the daily and weekly detectors for your most sensitive work.
How it works
- 1A Linear event fires when an issue is added to an epic.
- 2A filter confirms the parent is a tracked epic with a recorded baseline.
- 3Linear returns the epic's full current child-issue point total.
- 4Growth versus the kickoff baseline is computed including the new issue.
- 5A branch checks whether this addition crossed the threshold.
- 6Microsoft Teams alerts the lead with the epic, new total, growth percent, and the triggering issue.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect Microsoft TeamsChannels, chats, files.
- 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.