PROJECT MANAGEMENT
Scope-Creep Detector: Flag Issues Added After Sprint Start
Watches a Linear cycle and posts a Slack heads-up to the PM whenever an issue is added to the active sprint after it has already started.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue updated (webhook)Linear
- LogicIssue moved into active cycle after its start date?
- ActionFetch cycle committed vs. current estimateLinear
- LogicCompute added points and days into sprint
- OutputPost scope-creep heads-up to PM in SlackSlack
What it does
When an issue is assigned to the currently active Linear cycle after that cycle's start date, this workflow detects the late addition and pings the project manager in Slack with the issue, who added it, its estimate, and how many days into the sprint it landed.
When to use it
Run this on any team that commits to a fixed sprint scope. It catches the classic pattern where work quietly gets dragged into an in-progress cycle, inflating the committed point total and blowing the burndown without anyone signing off.
How it works
- 1A Linear webhook fires on every issue update.
- 2A logic step checks whether the issue's cycle is the active one and whether the cycle's start date is already in the past.
- 3If both are true, an action step pulls the cycle's original committed estimate vs. its current estimate from Linear.
- 4A logic step computes the added points and days-elapsed.
- 5A Slack message goes to the PM channel: issue link, requester, added estimate, and new committed total versus the sprint baseline.
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.