PROJECT MANAGEMENT
Flag and quarantine unattributed mid-sprint Linear additions
When a ticket is added to a committed sprint without a stakeholder attribution, this labels it as unattributed, removes it from the active cycle.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue added to active cycleLinear
- LogicPost-commit AND stakeholder field empty
- ActionLabel unattributed and remove from cycle in LinearLinear
- OutputEscalate to sprint lead in SlackSlack
What it does
Enforces a governance rule: nothing enters a committed sprint without a named owner of the request. Additions that arrive with no stakeholder field get tagged, pulled back out of the active cycle, and escalated to the lead so the team protects its commitment by default.
When to use it
Use it when scope creep is chronic and you want a hard gate rather than passive logging. Suited to teams whose leadership has agreed that mid-sprint work must be explicitly justified before it counts.
How it works
- 1A Linear webhook fires when an issue joins the active cycle.
- 2A filter keeps only post-commit additions, then checks whether the stakeholder field is empty.
- 3If empty, the flow applies an `unattributed-scope` label and removes the issue from the current cycle.
- 4It notifies the sprint lead in Slack with the issue and a request to attribute or reject it.
- 5The output is the escalation message; once a stakeholder is set, the issue can re-enter the cycle.
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.