PROJECT MANAGEMENT
Flag stalled cross-team handoffs blocking other teams' work
On a schedule, finds Linear issues that are blocking work owned by a different team but have sat idle past an SLA.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly business-hours schedule
- ActionFetch blockers with timestamps and team owners from LinearLinear
- LogicFilter to cross-team idle blockers past SLA
- LogicGroup offenders by blocking team
- OutputEscalate per-team handoff stalls in SlackSlack
What it does
Finds the worst kind of blocker: an issue owned by Team A that is blocking issues owned by Team B, yet hasn't been touched in days. These cross-team handoff stalls are where deadlocks usually start. The workflow surfaces each one and escalates it to the team actually holding up the others.
When to use it
Use it when teams routinely wait on each other and blame lands late. It enforces a handoff SLA: if you're blocking another team and idle past the threshold, you get pinged automatically.
How it works
- 1A schedule fires every few hours during work hours.
- 2Pull blocking issues from Linear along with last-updated timestamps and team ownership.
- 3Filter to issues where the blocker's team differs from the blocked issue's team and the blocker is idle past the SLA.
- 4Group the offenders by blocking team.
- 5Open one Slack thread per blocking team listing each stalled handoff and the downstream work it's freezing.
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.