PROJECT MANAGEMENT
Attach Loom design walkthrough to its Linear ticket with extracted acceptance criteria
When a designer posts a new Loom recording, this finds the matching Linear issue by key in the video title, embeds the Loom.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Loom recording publishedLoom
- LogicParse Linear issue key from video title
- ActionEmbed Loom link in Linear issueLinear
- ActionExtract acceptance criteria from transcriptOpenAI
- OutputWrite criteria as checklist on the ticketLinear
What it does
Turns a design walkthrough video into actionable engineering scope. The moment a Loom recording is published, the workflow locates the Linear issue referenced in the video title (e.g. "ENG-412 — Settings redesign"), embeds the Loom player in the issue description, pulls the spoken narration from the transcript, and converts it into a checked acceptance-criteria list right on the ticket.
When to use it
Use it when your design team hands off work by recording Looms and your engineers live in Linear. It removes the manual copy-paste of links and the guesswork of "what did the designer actually ask for" by capturing criteria the instant the video lands.
How it works
- 1A new Loom recording fires the trigger with its title, share URL, and transcript.
- 2A logic step parses the Linear issue key (e.g. ENG-412) from the title; if none is found the run stops.
- 3The Loom embed and link are appended to the matching Linear issue description.
- 4An LLM step reads the transcript and drafts discrete acceptance criteria.
- 5The criteria are written back to the Linear issue as a checkbox checklist.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 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.
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.