PROJECT MANAGEMENT
Capture mid-sprint Slack scope requests and gate them before they hit the ledger
When someone uses a scope-request slash command in Slack during an active sprint, this workflow estimates the ask, requires lead approval.
How it runs
The automated pipeline, trigger to output.
- TriggerSlack scope-request slash commandSlack
- LogicIs a sprint currently active?
- ActionSend approve/reject to sprint leadSlack
- LogicBranch on lead's decision
- ActionAppend approved ask to Notion ledgerNotion
- OutputCreate attributed Linear issue and reply in threadLinear
What it does
This turns informal "can we also squeeze in..." Slack asks into a governed intake. A scope-request submitted mid-sprint is sized, sent to the lead for an approve or reject decision, and only approved requests become a ledger entry plus a Linear issue tagged with the requester.
When to use it
Use it when scope creep starts as casual Slack messages that never get tracked. This forces every mid-sprint ask through one lane: estimated, approved or declined, and attributed.
How it works
- 1A Slack slash-command trigger fires when a teammate submits a scope request with a description and rough size.
- 2A logic step confirms a sprint is currently active and short-circuits to a friendly reply if not.
- 3An action posts an approve/reject interactive message to the sprint lead with the request and its estimate.
- 4A logic step branches on the lead's decision and exits on rejection with a note to the requester.
- 5An action appends the approved request to the Notion scope-creep ledger with points attributed to the requester.
- 6An output creates the Linear issue in the active cycle and links it back in the Slack thread.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect NotionPages, databases, comments.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.