PROJECT MANAGEMENT
Surface GitHub PR merge gridlock from stacked dependencies
Triggered on PR events, traces stacked/dependent pull requests across repos to detect merge gridlock — PRs each waiting on another to merge first.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub PR opened or ready webhookGitHub
- ActionFetch open PRs and dependency referencesGitHub
- LogicBuild PR graph and detect merge gridlock
- LogicCompute topological unblock order or exit
- OutputComment merge sequence on affected PRsGitHub
What it does
Maps dependency links between pull requests (stacked branches, "depends on #123" references, shared base branches) and detects gridlock where PRs are each waiting on another to land first. It then determines a safe merge order and posts it so engineers stop circling.
When to use it
Use it on teams that stack PRs or split features across repos, where it's easy to end up with three PRs that each politely wait for the others. Fires automatically whenever a PR is opened or marked ready, so gridlock is caught as it forms.
How it works
- 1A GitHub PR webhook (opened / ready-for-review) triggers the run.
- 2Fetch the open PR set and parse dependency references and stacked base branches.
- 3Build a PR dependency graph and detect cycles or unresolvable wait chains.
- 4If gridlock exists, compute a topological merge order that breaks it; otherwise exit.
- 5Comment the recommended unblock/merge sequence on each PR in the chain.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, 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.