PROJECT MANAGEMENT
Daily digest of Linear issues blocked by other teams
Each morning scans Linear for issues blocked by issues owned by a different team, ranks them by how long they've been stuck.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekday morning schedule
- ActionPull open issues with blocked-by linksLinear
- LogicFilter to cross-team blocks, compute age
- LogicRank by days stuck, group by blocking team
- OutputPost ranked digest to SlackSlack
What it does
Every weekday it walks Linear's blocking relationships, isolates the blocks where the blocker belongs to a different team than the blocked issue, and produces a single ranked digest of cross-team logjams sorted by days stalled.
When to use it
Use it when your teams use Linear's native blocks/blocked-by links and leads need one place each morning to see which of their issues are stuck waiting on another team, instead of clicking through every issue.
How it works
- 1A daily schedule trigger fires at a set hour on weekdays.
- 2The workflow pulls all open Linear issues that have an active blocked-by relationship.
- 3A logic step drops blocks where blocker and blocked share a team, keeping only true cross-team dependencies, and computes days-blocked for each.
- 4It ranks the survivors longest-stuck first and groups them by the blocking team.
- 5It posts the formatted digest to a Slack channel, with a deep link to each blocker issue.
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.