PROJECT MANAGEMENT
Daily cross-team blocked-dependency scan in Linear, alerted to Slack
Every morning, scans all Linear teams for issues marked blocked, traces which downstream issues depend on them, and posts a per-team digest of at-risk work to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule
- ActionFetch all blocked issues across Linear teamsLinear
- ActionResolve downstream issues that depend on each blockerLinear
- LogicDrop blockers with no downstream dependents
- LogicGroup at-risk issues by owning team
- OutputPost per-team risk digest to SlackSlack
What it does
Runs a daily sweep across every Linear team to find issues currently in a Blocked state, then walks each blocker's dependency links to identify the downstream issues that cannot move until it clears. It groups the findings by owning team and posts a clear digest to Slack so leads see their exposure before standup.
When to use it
Use it when work spans several Linear teams and a blocker on one team silently stalls another team's roadmap. It replaces the manual ritual of pinging other squads to ask whether your dependency is unblocked yet.
How it works
- 1A daily schedule fires the workflow each morning.
- 2The flow queries Linear for all issues in a Blocked state across every team.
- 3For each blocker it fetches the issues that declare a blocking relationship, building the at-risk downstream list.
- 4A filter drops blockers with no downstream dependents so the digest stays signal-heavy.
- 5Findings are grouped by the downstream issue's team.
- 6A formatted digest is posted to each team's Slack channel listing the blocker, its age, and the work it is holding up.
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.