PROJECT MANAGEMENT
Chat-driven blocker triage agent with Confluence brief
A chat-triggered agent investigates a named project's cross-project blockers across Asana and Linear, decides which are critical-path, and writes a triage brief to Confluence.
How it runs
The automated pipeline, trigger to output.
- TriggerChat request naming a project
- ActionGather project blockers from Asana and LinearAsana
- LogicTrace dependencies and assess critical path
- LogicClassify each blocker and draft an action
- OutputPublish triage brief to ConfluenceConfluence
What it does
You ask the agent in chat to triage a project. It gathers that project's blockers, traces each dependency into whatever other project or team owns it, reasons about which sit on the critical path versus which are slack, and publishes a written triage brief to Confluence with a recommended action per blocker.
When to use it
Use it before a milestone review or when you inherit a project and need a fast, reasoned read on what is actually at risk — not just a list, but a judgment call on what to fight for first.
How it works
- 1A chat message names the target project and kicks off the agent.
- 2The agent fetches the project's blocked tasks from Asana and any linked Linear dependencies.
- 3It follows each blocker to its owning project and assesses critical-path impact, owner responsiveness, and deadline pressure.
- 4It classifies each blocker as critical, watch, or low and drafts a recommended next action.
- 5It writes the structured triage brief to a Confluence page and replies in chat with the page link and the headline risks.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 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.