Dispatching Agent Work

Route work without coupling the decision to one vendor's model names or agent APIs. When dispatch mode is active, keep the current conversation as the coordinator and prefer a separate worker for substantive execution. Otherwise prefer the smallest execution unit and lowest sufficient model role that can meet the success criteria reliably.

Workflow

0. Confirm activation and duration

Proceed only when the current request or an authoritative host or repository instruction explicitly asks for dispatch or execution-boundary selection, or when a previously and explicitly established dispatch mode remains active in the conversation. Mentioning, reviewing, or editing this skill does not activate dispatch. Complexity, duration, cost, or possible parallelism alone does not activate it. When the current request provides no activation and no established dispatch mode is active, continue with the current agent under normal host policy.

Distinguish one-request activation from dispatch mode. A request to dispatch or delegate one objective applies only to that objective. A request such as "enter dispatch mode," "act as an orchestrator," or an authoritative instruction establishing that role activates dispatch mode for later objectives in the same conversation. Keep that mode active until the user asks to leave it or an authoritative instruction changes the role. Do not mistake a request to inspect, review, or edit this skill for activation.

In dispatch mode, treat the current agent primarily as a coordinator. Proactively dispatch every substantive objective that has a self-contained handoff and success criterion; the user does not need to repeat "dispatch" on each turn. Keep only clarification, routing, coordination, synthesis, and genuinely trivial one-step actions in the current conversation. Do not create an empty worker merely to await an objective: collect enough task content for a lean handoff first.

Activation permits routing analysis but does not override host policy or broaden authority. Before considering a boundary, remove any backend that the host forbids or that requires authorization not present in the current request.

1. Capture the dispatch contract

Extract only: