PROJECT MANAGEMENT
Triage Mid-Sprint Requests From Slack
When someone posts a new work request in a Slack channel during an active sprint, an agent assesses urgency and size.
How it runs
The automated pipeline, trigger to output.
- TriggerNew message in Slack intake channelSlack
- LogicAgent classifies request vs chatter
- ActionAgent estimates size and urgency
- LogicBranch deferrable vs urgent
- ActionDraft backlog issue for next sprintLinear
- OutputEscalate urgent ask with swap recommendationSlack
What it does
Listens for new work requests in a designated Slack channel while a sprint is in progress. An agent reads the request, estimates rough size, and judges whether it is a genuine emergency or deferrable. Deferrable items become drafted backlog issues; urgent ones are escalated with a recommendation so the lead can make a deliberate swap rather than silently expanding scope.
When to use it
Use this when stakeholders drop asks into Slack mid-sprint and the team's default is to just absorb them. It forces every incoming request through a defer-or-decide gate.
How it works
- 1A Slack trigger fires on messages in the intake channel.
- 2An agent classifies the message as a real work request versus chatter and drops non-requests.
- 3The agent drafts a size estimate and an urgency judgment with reasoning.
- 4A branch separates deferrable from urgent requests.
- 5Deferrable requests are written to Linear as backlog issues tagged for next sprint.
- 6Urgent requests post a threaded Slack escalation summarizing the ask, estimate, and a swap recommendation for the lead.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.