PROJECT MANAGEMENT
Quarterly cross-team RACI health agent with Confluence report
On a quarterly schedule, an agent inventories every active initiative across Asana, identifies missing or duplicated accountability, drafts remediation recommendations.
How it runs
The automated pipeline, trigger to output.
- TriggerQuarterly schedule starts agent run
- ActionEnumerate active Asana projects and accountability fieldsAsana
- LogicAgent reasons over coverage gaps, SPOFs, and conflicts
- ActionPublish RACI health report to ConfluenceConfluence
- OutputLink leadership to the report in SlackSlack
What it does
An agent performs a deep quarterly review of accountability across all active initiatives. It reads each Asana project, reasons about where Responsible or Accountable coverage is missing, where one person is over-allocated as Accountable, and where two people claim the same Accountable role, then writes a structured RACI health report to Confluence with prioritized recommendations.
When to use it
Use it for leadership operating reviews where you need a narrative, not just a list. Best when ownership clarity is a recurring organizational risk and you want an analyst-quality assessment each quarter without a human spending a day on it.
How it works
- 1A quarterly schedule starts the agent run.
- 2The agent enumerates active Asana projects and their assignees and accountable fields.
- 3It reasons over the data to find unowned work, single-points-of-failure owners, and conflicting Accountable claims.
- 4It drafts a report with findings ranked by impact and concrete reassignment suggestions.
- 5The report is published as a new Confluence page under the leadership space.
- 6A Slack message links leadership to the published report.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.