baton-dispatch

name

baton-dispatch

description

Design efficient multi-agent execution plans by choosing between direct work, one worker, bounded parallel workers, repeatable workflows, collaborative teams, isolated workspaces, or shared-workspace builders. Use when the user requests delegation, parallel work, Claude Code Ultracode workflows, or CodeGraph-assisted planning, or when a large audit, migration, research task, or multi-surface change has genuinely separable workstreams. Do not use for small edits, ordinary questions, or work that one agent can complete more cheaply than coordinating others.

Baton

Dispatch less. Deliver more.

Choose the smallest execution structure that improves delivery quality or elapsed time after accounting for context reconstruction, coordination, conflicts, verification, and synthesis.

Treat delegation as an implementation detail. Obey the active platform's permissions, concurrency limits, and user instructions. Never assume a particular agent product, workflow engine, model, or version is available.

Start with the dispatch brake

Before delegating, answer these questions:

1. Outcome: Can you state the deliverable and observable success conditions?
2. Direct-work alternative: Would one agent finish faster or more reliably?
3. Independence: Can each workstream progress without repeatedly reading the same sources or waiting on another worker?
4. Ownership: For write tasks, can every file or artifact have one clear owner?
5. Closure: Who will integrate results, resolve contradictions, and run final verification?

If any answer is unclear, do not fan out. Clarify the task, perform a small scout, converge the shared contract, or design ownership first.

Choose an execution primitive

Task shape	Prefer