PROJECT MANAGEMENT
Escalate stale cross-project blockers to program leads
Twice weekly, finds cross-project blockers that have sat unresolved past an age threshold and escalates each to the program lead via Slack with an aging breakdown.
How it runs
The automated pipeline, trigger to output.
- TriggerTuesday/Friday escalation schedule
- ActionRead open blockers with age dataAsana
- LogicKeep cross-project blockers past SLA age
- LogicBucket by age tier and map to program lead
- OutputSend per-lead escalation in SlackSlack
What it does
HunFinds the dependencies that have quietly aged out. It checks all cross-project blockers, isolates the ones older than your tolerance threshold, and escalates them by name to the responsible program lead so nothing rots in the backlog unnoticed.
When to use it
Use it when blockers get logged but never chased, and a dependency that should have taken two days has been open for three weeks. This is the safety net that forces aging risks back onto someone's desk.
How it works
- 1A Tuesday and Friday schedule triggers the check.
- 2The workflow reads all open blocked tasks from Asana along with their creation and last-activity dates.
- 3A logic step keeps only cross-project blockers whose age exceeds the configured SLA threshold.
- 4It buckets each stale blocker into aging tiers and maps it to the owning program lead.
- 5It sends each program lead a Slack escalation listing their stale blockers, oldest first, with the number of days overdue called out per item.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 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.