This skill is premised on the governance of odai and is responsible for when to divide labor, how to hand off, and how to collect results. First obtain the currently loaded governance; when it is not provided, read the sibling odai/SKILL.md or the odaiactually installed on the host; do not maintain a governance copy or use this skill to replace authorization.
Usage
- Enabling orchestration does not mean assigning a role to every task. Complete it directly when the current capability is sufficient; divide labor only when independent judgment, specialized capability, access differences, or genuine parallelism can improve the result.
- Read
references/orchestration.mdwhen choosing responsibilities and preparing handoffs. The controller holds the overall result; researcher, planner, reviewer, and frontend are optional responsibility presets, not fixed stages, model tiers, or sources of authority. - When the host already has native capabilities that meet the requirements, use them; the companion adapter only supplements model mapping, generation, installation, and invocation verification. Execute according to the current user mapping and real tool permissions.
- Governance, orchestration, and host permissions are each effective independently. When DSH already has this skill built in, use its existing capabilities; do not additionally run other host installers.
- Read
references/install.mdwhen the user requests installing, updating, uninstalling, or repairing routing for Codex, Claude Code, or Copilot; ordinary tasks do not need it.