PROJECT MANAGEMENT
Capture Standup Commitments from Slack and Register Them as Linear Dependencies
Watches a team's daily standup channel for sentences where someone promises to deliver something to another team.
How it runs
The automated pipeline, trigger to output.
- TriggerNew message in standup Slack channelSlack
- LogicLLM extracts deliverable promises (owner, recipient, due date)OpenAI
- LogicFilter out messages with no commitment
- ActionCreate Linear issue with assignee, due date, dependency labelLinear
- OutputReply in Slack thread confirming the tracked commitmentSlack
What it does
Reads new messages in your standup or daily-sync Slack channel, uses an LLM to spot commitments ("I'll have the API spec to the mobile team by Thursday"), and turns each one into a Linear issue labeled `cross-team-dependency` with the committer as assignee, the inferred due date, and the requesting team as a linked label. The original Slack message is linked back so context is never lost.
When to use it
When promises made verbally in standups quietly evaporate and the receiving team is left blocked with no paper trail. Best for orgs running async or written standups where one team's deliverable gates another's work.
How it works
- 1A new message posts in the designated standup channel.
- 2An LLM classifies the message: does it contain a deliverable promise (who owes what, to whom, by when)? Non-commitments are dropped.
- 3For each promise, the flow resolves the committer's Slack identity to a Linear user.
- 4A Linear issue is created with assignee, due date, the `cross-team-dependency` label, and a permalink to the source message.
- 5A threaded Slack reply confirms the captured commitment and links the new issue.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect OpenAIModels, embeddings, files.
- 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.
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…
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.
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.
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.