PROJECT MANAGEMENT
Circular Blocked-By Cycle Detector Across Linear Projects
Scans all open Linear issues nightly, builds a blocked-by dependency graph, and flags any circular chain (A blocks B blocks C blocks A) that can never resolve on its own.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionFetch open issues + blocked-by links from LinearLinear
- LogicBuild dependency graph and detect cycles
- LogicBranch: any cycle found?
- ActionResolve assignees and project leads from LinearLinear
- OutputPost each cycle to Slack escalation channelSlack
What it does
A circular blocked-by chain is a silent project killer: every issue in the loop is waiting on another issue in the same loop, so none of them can ever start. This workflow walks the entire Linear dependency graph on a schedule, detects every cycle, and surfaces it to the right people before a sprint stalls.
When to use it
Run it when multiple teams file cross-project dependencies and no single person owns the whole graph. Ideal for orgs where Linear issues frequently carry "blocked by" links across team boundaries.
How it works
- 1A nightly schedule fires the run.
- 2Fetch all non-completed issues and their blocked-by relations from Linear.
- 3Build an in-memory directed graph and run cycle detection (DFS / Tarjan) to find every strongly-connected loop.
- 4A branch checks whether any cycle was found; if none, the run exits quietly.
- 5For each cycle, resolve the assignees and project leads of the involved issues.
- 6Post a formatted Slack message per cycle listing the loop path and tagging the leads to 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
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.
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.
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.
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…
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.