PROJECT MANAGEMENT
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.
How it runs
The automated pipeline, trigger to output.
- TriggerNew GitHub PR review commentGitHub
- LogicLLM detects cross-team blocker and owning teamOpenAI
- LogicFilter out non-blocker comments
- ActionCreate Linear dependency issue linked to the PRLinear
- OutputNotify owning team in SlackSlack
What it does
Listens for new GitHub PR review comments and detects when one team is blocked waiting on another ("can't merge until the platform team ships the auth endpoint"). It creates a Linear issue capturing the blocking relationship, assigns it to the owning team, sets a due date if the comment names one, and posts the blocker to that team's Slack channel.
When to use it
When engineering handoffs that surface in code review never make it onto anyone's board, so PRs sit stale waiting on a dependency no one is tracking. Best for orgs where cross-team blockers regularly appear in review threads.
How it works
- 1A GitHub webhook fires on a new PR review comment.
- 2An LLM classifies whether the comment describes a cross-team blocker and extracts the owing team and any named date.
- 3Non-blocker comments are filtered out.
- 4A Linear issue is created describing the blocker, assigned to the owning team with a due date and link to the PR.
- 5The blocker is posted to the owning team's Slack channel with the PR and issue links.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 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.
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.
Daily Retro Sweep to Themed Notion Action Board
On a schedule, finds yesterday's Zoom retro recordings, transcribes them, and appends themed, owner-tagged action items as rows in a Notion board database.
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.