Project Management
Subagent DAG Orchestration
Use when delegated work breaks into several tasks that agents on the roster can carry out. The host's role decides what to delegate; this skill decides how to group that work. A DAG node dispatches to a roster agent, including the generic agent, and cannot call the host's tools. Choose from the tool's `subagent` parameter enum -- agent names on ordinary turns, worker labels when a Worker Table is bound. The roster describes underlying capabilities. Reading a brief or checking task status is host coordination, not a reason to create graph nodes. Before dispatching tasks one at a time, test three things: are two or more tasks independent (they can run at once), does a task hand its result to the next (a graph wires that handoff with no turn of yours in between), do the tasks want different specialists (the roster closes the tool list). If any of the three holds, orchestrate the whole task as one run_subagent_dag call. A step whose result decides what runs next is a decision node: give it routes, and guard what follows with when, all in one graph. Iteration is graphs in series, one graph per round, driven by you.
- Publisher / source
- EverMind-AI/Raven (found on GitHub top repositories)
- Upstream record
- EverMind-AI/Raven
- Version
- Version 1
- Published
- Publication review
- Approved for publication · recorded passed scan 2026-11-04
- Content fingerprint
9a43443c052f27f6bf21f238fb423d7790478f8abbfeb564159b65a5def3be0f