PROJECT MANAGEMENT
AI weekly briefing on dependency bottlenecks across tools
Each week, an agent reads dependencies from Asana and GitHub, reasons about which tasks block the most downstream work.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionFetch dependencies from Asana and GitHubAsana
- ActionPull linked PRs and issues from GitHubGitHub
- LogicScore bottlenecks by downstream impact and draft briefingOpenAI
- OutputPost bottleneck briefing to SlackSlack
What it does
An agent pulls task dependencies from Asana and linked engineering work from GitHub, then reasons across them to explain — in plain language — which items are the real bottlenecks: the ones blocking the most downstream work or sitting on the longest chains. It produces a narrative briefing, not just a list, including suggested owners and next actions.
When to use it
Use it for a Monday leadership or PM briefing when raw blocker lists are too noisy to act on. The agent prioritizes by downstream impact and writes the "so what," which a deterministic report can't.
How it works
- 1A weekly schedule starts the agent.
- 2The agent fetches tasks and dependencies from Asana and related PRs/issues from GitHub.
- 3It scores each item by downstream blocking impact and chain depth, and identifies likely deadlock risks.
- 4It drafts a prioritized briefing with reasoning and recommended owners.
- 5It posts the briefing to a Slack channel for the weekly review.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect OpenAIModels, embeddings, files.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.
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…
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.
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.
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.