PROJECT MANAGEMENT
Flag Linear issues a teammate keeps mentioning on Loom but never moves
Tracks issues referenced across consecutive Loom standups and flags any that have been talked about repeatedly while showing zero Linear movement.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule triggers analysis
- ActionFetch past week's Loom standup transcriptsLoom
- ActionMap issues referenced per person and frequencyOpenAI
- ActionPull weekly Linear activity for those issuesLinear
- LogicFlag repeatedly-mentioned, never-moved issues
- OutputPost weekly stuck-work callout to SlackSlack
What it does
Over a rolling week it links the issues people mention in their Loom standups to actual Linear activity. When the same issue is referenced in multiple standups but its Linear status, comments, and commits stay flat, it gets flagged as stuck. A weekly callout names the chronically-stalled work so it can be unblocked or dropped.
When to use it
When work keeps getting mentioned ('still on the auth migration') but never visibly progresses, and you want data instead of a hunch about what's truly stuck.
How it works
- 1A weekly schedule triggers the analysis.
- 2Loom returns the past week's standup transcripts.
- 3An agent maps which issues each person referenced and how often.
- 4Linear activity for those issues over the same week is pulled.
- 5Logic flags issues mentioned repeatedly with no state, comment, or commit movement.
- 6A weekly stuck-work callout is posted to the team Slack channel.
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.
- 4Connect OpenAIModels, embeddings, files.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.