mass-ulw

name	mass-ulw
description	Run a dependency graph of child agents in one call with the native dag tool. Use when the user asks for mass-ulw, a DAG of tasks, fan-out/fan-in work, or multi-agent execution where some tasks must wait on others.
metadata	{"short-description":"Dependency-graph orchestration of child agents"}

mass-ulw

Use this skill when the user asks for mass-ulw, a task DAG, staged fan-out, or any multi-agent job where real dependencies exist: task C needs A and B finished first. For fully independent workers, plain parallel task spawns are simpler. Reach for dag when the ordering itself is the point.

The shape

A run is a declarative definition: a stable key (idempotency: re-starting the same key with the same graph reuses the run), a human name, and nodes. Each node has an id, a self-contained English prompt, a category that routes it to the right kind of worker, and optional dependsOn listing node ids that must finish first. dependsOn is ordering ONLY: no upstream output is substituted into a downstream prompt, so write every prompt to stand alone. Optional per-node extras: label, task_summary, description, and load_skills (skill names prepended to that node's prompt).

Route every node by category. Pick the category whose job description matches the node's work; the run executes nodes in parallel waves as their dependencies clear.

JS SDK

JS cells import the SDK from the path the extension publishes:

const sdk = await import(`${env("OMO_DAG_SDK_ROOT")}/sdk.js`)

const dag = sdk.define({ key: "docs-refresh", name: "Docs refresh" })
dag.node({ id: "audit", category: "explore", prompt: "Audit docs/ for stale API references and list each stale file with the outdated claim." })
dag.node({ id: "rewrite", category: "writing", prompt: "Rewrite every stale page under docs/ against the current API surface in src/.", dependsOn: ["audit"] })
dag.node({ id: "verify", category: "quick", prompt: "Check every code sample under docs/ compiles and every internal link resolves.", dependsOn: ["rewrite"] })

const run = await sdk.start(dag)
const result = await sdk.wait(run.run_id)

define builds the definition and rejects duplicate node ids locally, before anything is started. start, attach, snapshot, wait, and cancel are the whole surface.

Python

Python can't import an ESM module, so there's no SDK there. Call the tool directly with plain dicts:

run = tool.dag({
    "action": "start",
    "definition": {
        "key": "docs-refresh",
        "name": "Docs refresh",
        "nodes": [
            {"id": "audit", "category": "explore", "prompt": "Audit docs/ for stale API references and list each stale file with the outdated claim."},
            {"id": "rewrite", "category": "writing", "prompt": "Rewrite every stale page under docs/ against the current API surface in src/.", "dependsOn": ["audit"]},
            {"id": "verify", "category": "quick", "prompt": "Check every code sample under docs/ compiles and every internal link resolves.", "dependsOn": ["rewrite"]}
        ]
    }
})
result = tool.dag({"action": "wait", "run_id": run["run_id"]})

Run lifecycle

start returns a run_id and a snapshot; keep the id. From there:

const sdk = await import(`${env("OMO_DAG_SDK_ROOT")}/sdk.js`)
const runId = "run_stub_1"
await sdk.attach(runId)
await sdk.snapshot(runId)
await sdk.cancel(runId, "superseded by a new plan")

• attach re-binds to a live run you already own, for example after your own context was rebuilt.
• snapshot is a cheap read of status and node counts; poll it instead of wait when you have other work to do.
• wait blocks until the run settles and returns the final result.
• cancel stops the run; pass a reason so the record says why.

Resume across a restart

Runs are journaled. When the session dies mid-run, the run pauses instead of being lost; on restart the extension resumes paused runs it owns, reusing outputs of nodes that already finished so completed work is never redone. Your side of the contract: start with the same key and definition returns the existing run (reused: true) instead of forking a duplicate, or attach with the stored run_id. Never re-issue a changed definition under an old key; that's a definition conflict.

Observing a run

• The TUI status widget shows live runs with per-node progress.
• /dag opens the detail view: node states, waves, and failures for each run in the session.
• External viewers subscribe to the RPC channels omo.dag.event (journaled, sequenced), omo.dag.updated (full snapshots), omo.dag.heartbeat, and omo.dag.activity.