PROJECT MANAGEMENT
Agent-Driven Retro Follow-Up with Owner Negotiation
An agent reviews the Zoom retro transcript against the team's open Linear backlog, drafts themed action items.
How it runs
The automated pipeline, trigger to output.
- TriggerZoom retro recording completedZoom
- ActionAgent extracts themes and candidate itemsOpenAI
- ActionCross-check against open Linear backlogLinear
- ActionDM proposed owners to confirm scope and due dateSlack
- LogicInterpret owner replies and finalize commitments
- OutputCreate confirmed assigned Linear issuesLinear
What it does
This agent-driven workflow does more than transcribe a retro. It reads the Zoom transcript, compares the surfaced topics against the team's existing Linear backlog to avoid duplicate work, and drafts a themed set of proposed action items. Before creating anything, the agent reaches out to each proposed owner over Slack to confirm ownership and a realistic due date, then creates the agreed Linear issues.
When to use it
Use it when your retros produce ambiguous or contested ownership and you want a human-in-the-loop step. The agent handles the back-and-forth of confirming who owns what, so the resulting board reflects real commitments rather than guesses.
How it works
- 1A Zoom recording-completed event fires for the retro.
- 2The agent fetches the transcript and reasons over themes and candidate action items.
- 3It cross-checks the candidates against open Linear issues to drop duplicates.
- 4For each remaining item, the agent DMs the proposed owner on Slack to confirm scope and due date.
- 5A logic step waits for and interprets each reply.
- 6Confirmed items are created as assigned, themed Linear issues.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 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.