PROJECT MANAGEMENT
Standup Blockers to Linear Handoff Issues
Scans collected Discord standup replies for stated blockers and handoffs, then creates a Linear issue for each one with the blocked person and the owner they're waiting on.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires after standup cutoff
- ActionPull the day's standup replies from DiscordDiscord
- ActionExtract structured blockers and named ownersOpenAI
- LogicKeep only replies that contain a real blocker
- ActionCreate a Linear issue per blocker, assign ownerLinear
- OutputPost linked blocker summary back to DiscordDiscord
What it does
Turns the "I'm blocked on..." lines buried in async standups into tracked work. After the standup window closes, it parses each reply, extracts blockers and cross-person handoffs, and opens a Linear issue per blocker so nothing is lost between timezones.
When to use it
Use it when blockers raised in Discord standups quietly evaporate because the person who could unblock them is asleep. This guarantees every blocker becomes a tracked, assignable Linear issue with a clear waiting-on relationship.
How it works
- 1A schedule fires shortly after the standup collection cutoff.
- 2The workflow pulls the day's standup replies from the Discord channel.
- 3An LLM step extracts structured blockers: who is blocked, what they need, and who they named as the owner.
- 4A filter drops replies with no blocker so only real handoffs proceed.
- 5For each blocker it creates a Linear issue titled with the ask, assigned to the named owner, labeled "standup-blocker."
- 6It posts a summary back to Discord linking each new issue.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.