PROJECT MANAGEMENT
Flag Linear issues added after sprint commit
Watches a Linear active cycle and flags any issue added or moved into the cycle after the sprint was committed, tagging it as scope creep and posting a running tally to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue added to active cycleLinear
- LogicCompare assignment time to cycle commit timestamp
- ActionLabel issue scope-creep and comment actor + timeLinear
- OutputPost late-add alert and creep tally to SlackSlack
What it does
Monitors the currently active Linear cycle and detects issues that appear in it after the sprint commit timestamp. Each late arrival gets a `scope-creep` label, a comment noting when and by whom it was added, and a running count is pushed to the team's Slack channel so the addition is visible the moment it happens.
When to use it
For teams that commit to a fixed cycle scope at sprint planning but routinely find work sneaking in mid-sprint. Use it when you want creep caught in real time rather than discovered during retro.
How it works
- 1A Linear webhook fires when an issue is created in or moved into the active cycle.
- 2The flow reads the cycle's committed-at timestamp and compares it to the issue's cycle-assignment time.
- 3If the issue landed after commit, it's flagged as creep; if it was part of the original commit, the flow exits.
- 4The flagged issue is labeled `scope-creep` and annotated with the actor and timestamp via the Linear API.
- 5A Slack message announces the new addition and the cycle's updated creep count.
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.