PROJECT MANAGEMENT
Weekly cross-project blocker digest for risk review
Every Monday morning, scans all active projects for tasks blocked by dependencies in other projects, ranks them by impact, and posts a structured risk-review digest to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerMonday 7am weekly schedule
- ActionFetch all blocked tasks across projectsAsana
- LogicKeep only cross-project blockers
- LogicRank by downstream impact and due date
- OutputPost ranked digest to risk-review channelSlack
What it does
Pulls every open task across your Asana portfolio that is blocked, identifies which blockers live in a *different* project than the work they hold up, then compiles a ranked digest and drops it into your weekly risk-review Slack channel before the meeting starts.
When to use it
Run this when your weekly risk or program review keeps getting blindsided by cross-team dependencies nobody flagged. It replaces the manual spreadsheet someone builds every Friday and guarantees the room walks in with the same picture.
How it works
- 1A Monday 7am schedule fires the workflow.
- 2It queries Asana for all incomplete tasks carrying a dependency or "blocked" marker across active projects.
- 3A logic step keeps only blockers whose source task sits in a different project than the blocked task — the true cross-project risks.
- 4It scores each by downstream task count and due-date proximity to rank severity.
- 5It formats a digest grouped by owning team with the top risks surfaced first.
- 6The digest is posted to the #risk-review Slack channel as a threaded message ready for discussion.
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.