PROJECT MANAGEMENT
Weekly cross-tool dependency rollup for program review
Once a week, an agent aggregates blocked items from Asana, Linear, and a Coda tracker, reconciles duplicates across tools.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly pre-review schedule fires
- ActionPull blockers from Asana, Linear, and CodaAsana
- LogicDedupe cross-tool items and rank by risk
- ActionDraft plain-English program briefCoda
- OutputPost review brief to program-leads SlackSlack
What it does
This agent-driven workflow gathers blocked and dependency-tagged work from Asana, Linear, and the Coda tracker, then reconciles items that appear in more than one tool into a single view. It reasons about which stalled handoffs carry the most schedule risk and writes a concise program-review brief — top blockers, the teams on each side, how long they've been stuck, and a suggested owner for each.
When to use it
Run it ahead of the weekly program review when dependencies live in several tools and leads need one synthesized narrative instead of three raw exports.
How it works
- 1A weekly schedule triggers the run before the review meeting.
- 2The agent pulls open blockers from Asana, Linear, and the Coda tracker.
- 3It dedupes items that reference the same dependency across tools.
- 4It ranks the remaining blockers by stall duration and downstream impact, drafting a plain-English summary with recommended next owners.
- 5It posts the finished brief to the program-leads Slack channel for the meeting.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect CodaDocs, packs, automations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.