Multi-Agent Orchestration
Use workers only when the host and user permit delegation. Parallel tasks must be genuinely independent. An explicitly requested sequential reviewer is also a supported coordination pattern; it does not authorize parallel editing.
Read client mapping when selecting a client-specific coordination mechanism or inspecting its usage and permission boundaries. Read candidate comparison only when several independent implementations can be tested against one rubric. Read coverage fanout only when independent review lenses can inspect the same pinned artifact without overlapping writes.
Workflow
- Confirm delegation authority, supported host behavior, budget or cost constraints, and the integration owner. State the planned worker count and expected cost or time before launching, and get agreement when they exceed what the user implied.
- Decompose the work into bounded tasks with clear inputs, outputs, owned files or read-only scope, stopping conditions, and required evidence. Match each worker's capability and cost to its task, and brief each worker completely the first time.
- Identify dependencies. Keep tightly sequential work with one owner.
- Prevent overlapping write ownership and state which worker may modify each shared artifact.
- Launch only useful independent tasks and retain meaningful local integration work.
- Require workers to report evidence, limitations, changed files, validation, and unresolved risks.
- Before waiting on a worker, command, or hook, confirm it is still running and making progress, and set a limit on the wait. If it stalls, report it as a blocker with its last output instead of checking it in a loop.
- Reconcile results against the shared objective. Independently inspect diffs and rerun integration gates.
- Stop when tasks conflict, authority changes, costs exceed the agreed bound, or external decisions are required.
One optional reviewer
Worker and session limits bound authorized work, not every inference request made by the client. Allow for client-managed summaries, memory generation, retries, and other overhead when estimating usage; leave unmeasured amounts unknown. Distinguish planned work, observed requests and tokens, and account billing or allowance evidence. A token estimate is not a bill or a verified spending cap. Do not enable telemetry, alter runtime controls, or launch a measurement task merely to fill an evidence gap.
For a bounded review of one change, the owner keeps implementation responsibility. Before launching, verify the actual host, effective custom-agent permissions, model configuration, data exposure, and absence of paid fallback. Use one read-only reviewer at a time; prohibit nested delegation, edits, external replies, publication, and merge. Do not install an agent or change settings to enable it.
Pass the outcome, acceptance conditions, exact base/head, relevant working-tree snapshot, findings ledger, and available rounds. Include affected callers and contracts rather than only changed lines. The default is three review rounds across self-review and delegated attempts per maintenance invocation. Failed or unusable delegated attempts consume a round. Preserve the count across new heads, comments, and resumed sessions; extensions require explicit authority. Record a round as started before dispatch and retain its identifier/outcome. An uncertain dispatch consumes a round; reconcile it before launching any replacement.
Verify host-supported deadline and stop controls before dispatch. The reviewer must fit the remaining CI/review wait allowance (30 minutes by default); otherwise the lane is unavailable. Charge its pending elapsed time, including owner work, without double-counting overlapping waits. On timeout, cancellation, or an authority or billing failure, stop only this task's reviewer and read back its status. Keep unconfirmed shutdown unresolved. Do not cancel hosted CI or unrelated workers.
If the optional reviewer is unavailable, report the limitation and continue permitted owner work. If independent review is required, leave it blocked. Never silently fall back to another account, proxy, API, or billing route. Worker success is evidence to assess, not human approval or permission for another action.
Forbidden delegation
- Do not delegate without user or host authorization.
- Do not assign multiple workers to edit the same owned files.
- Do not delegate irreversible publication, deletion, deployment, or merge decisions.
- Do not treat worker completion as verified integration.
- Do not parallelize work whose outputs depend tightly on earlier unfinished steps.
Output
Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.
Lead with the integrated result and anything that needs the user's decision. Then return Delegation authority, Task map, Ownership, Evidence contract, Cost boundary, Worker results, Integration verification, and Unresolved decisions. List a decision as unresolved only when it blocks remaining work; otherwise make the routine call, record it, and continue.
Example
Synthetic example; not an observed client result.
Input: Two agents are authorized to review independent API and storage changes.
Output: Give each agent a distinct artifact and evidence contract, then reconcile findings against one revision. Keep shared edits with one owner.