PROJECT MANAGEMENT
Detect circular blocking chains in Linear and alert the owners
Scans Linear issue blocking relationships on a schedule, detects circular dependency loops (A blocks B blocks A).
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionFetch issues and blocking relations from LinearLinear
- LogicBuild dependency graph and detect cycles
- LogicExit if no cycles found
- OutputPost each cycle and its owners to SlackSlack
What it does
Walks every "blocks"/"blocked by" relationship across your Linear workspace and finds cycles — chains of issues that block each other in a loop and can never complete on their own. Each detected loop is posted to Slack naming the issues, the teams, and the assignees stuck in the deadlock.
When to use it
Run it when cross-team work keeps stalling and nobody can say why. Circular blockers are invisible in a normal board view because each issue looks merely "blocked." Schedule it daily so a new loop is caught the morning after it forms, before it silently freezes a release.
How it works
- 1A daily schedule fires the workflow.
- 2Pull all active issues and their blocking relations from Linear.
- 3Build a dependency graph in code and run cycle detection; if no cycles exist, the run exits quietly.
- 4For each cycle, resolve the full loop path with issue IDs, titles, teams, and assignees.
- 5Post one Slack message per loop tagging every assignee in the cycle so an owner can break it.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.