PROJECT MANAGEMENT
Flag mid-sprint Linear issues added after sprint start
Watches a Linear cycle and, whenever an issue is added to it after the cycle has already begun, posts a scope-creep alert to Slack with the issue's estimate, author…
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue added to or updated in a cycleLinear
- LogicKeep only issues added after the cycle start date
- ActionFetch cycle's current issue count and total estimateLinear
- LogicCompute added points and % increase vs committed scope
- OutputPost scope-creep alert to the squad Slack channelSlack
What it does
Detects when work is injected into an in-progress Linear cycle. Every time an issue is moved into the active cycle after its start date, the workflow checks whether the cycle is already underway and, if so, raises a scope-creep flag with the details the lead needs to decide whether to accept or defer it.
When to use it
Run this on any squad that commits to a fixed scope at sprint planning and wants discipline about additions. It turns silent mid-sprint adds into a visible, point-quantified signal instead of a surprise at retro.
How it works
- 1**Trigger** — Linear fires when an issue is added to or updated within a cycle.
- 2**Logic** — Compare the issue's added-at timestamp against the cycle start date; pass only issues injected after the cycle began.
- 3**Action** — Fetch the cycle's current scope (issue count and summed estimate) from Linear.
- 4**Logic** — Compute the added points and the percentage increase over the originally committed total.
- 5**Output** — Post a Slack alert to the squad channel naming the new issue, its estimate, who added it, and the revised cycle 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.