orchestratinglisted

# Orchestrating Delegate only when coordination value exceeds its overhead. Keep a no-op, one bounded task, or sequential dependency path inline. Scan dependencies, boundaries, ownership, and oracle before dispatch. Invoking this skill explicitly authorizes native agents for matching lanes. Use one to three direct children with fresh, bounded context by default. For two or more independent lanes whose results cannot reshape one another, issue native spawn calls consecutively. Do not inspect output, wait, or begin deep lane work between spawns. After dispatch, continue useful lead-owned work that is independent of the lanes. Track every returned identity and later join each until it completes, fails, or its cancellation is confirmed. Before dispatch, read [native dispatch examples](references/native-dispatch.md) and use only the active harness's call shape. One bounded output-only lane may use one fresh-context child returning `verdict`, `evidence`, `uncertainty`, and `next`. Keep bulky raw payloads in an artifact. Route unknown causes through `systematic-debugging`, unresolved contracts through `design-and-plan`, external evidence through `evidence-research`, cross-provider risk through `independent-review`, and effects through `safe-effects`. Preflight tools, authentication, permissions, and write authority. Brief the outcome, bounded and disjoint ownership, constraints, oracle, prohibited scope, return condition, and nested-delegation limit. Shared writes and Git stay