PROJECT MANAGEMENT
Daily stalled-handoff digest to program leads
Each morning, scans Linear for cross-team dependency issues that haven't moved in N days and posts a grouped digest to the program leads' Slack channel so stalled handoffs get…
How it runs
The automated pipeline, trigger to output.
- TriggerWeekday morning schedule fires
- ActionQuery Linear for dependency-labeled issuesLinear
- LogicKeep only issues stalled past the window
- LogicGroup by blocking team, sort by days stalled
- OutputPost grouped digest to program-leads SlackSlack
What it does
Every weekday morning this workflow pulls all Linear issues labeled as cross-team dependencies, finds the ones whose status hasn't changed within your staleness window (default 3 business days), and posts a single grouped Slack digest to your program-leads channel. Each entry shows the blocking team, the waiting team, days stalled, and a direct link.
When to use it
Run this when handoffs between squads keep silently stalling and nobody notices until a sprint review. It gives program leads one scannable list every morning instead of forcing them to hunt across boards.
How it works
- 1A schedule fires on weekday mornings before standup.
- 2The workflow queries Linear for open issues carrying the "dependency" or "blocked" label.
- 3A staleness filter keeps only issues with no state transition inside the configured window.
- 4Remaining issues are grouped by blocking team and sorted by days stalled.
- 5A formatted digest is posted to the Slack program-leads channel; if nothing is stale, it posts a short all-clear note so leads know the check ran.
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.