PROJECT MANAGEMENT
Triage a Loom design handoff and route it to the right Linear team with scoped subtasks
An agent watches for new Loom handoffs, decides which engineering team owns the work, creates a parent Linear issue with the embedded Loom.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Loom recording publishedLoom
- LogicAgent classifies owning team from transcript
- ActionCreate parent Linear issue with Loom embedLinear
- ActionGenerate scoped subtasks as child issuesLinear
- OutputNotify owning team in SlackSlack
What it does
Acts as an intake agent for incoming design handoffs. When a Loom walkthrough is published, the agent reads the transcript, determines which engineering team (frontend, backend, platform) should own the work, opens a parent Linear issue in that team with the Loom embedded, and decomposes the spoken requirements into scoped subtasks.
When to use it
Use it when handoffs arrive without a clear owner and a person has to manually route and break down each one. It fits multi-team orgs where the right team is inferable from the content of the walkthrough rather than a fixed mapping.
How it works
- 1A new Loom recording triggers the agent with title and transcript.
- 2The agent classifies the work and selects the owning Linear team, branching on its decision.
- 3It creates a parent Linear issue in that team with the embedded Loom and a summary.
- 4It generates subtasks from the discrete requirements in the narration.
- 5It posts each subtask as a child issue and notifies the team channel in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.