multi-agent-orchestrator
Multi-Agent Orchestrator
Use this skill when the current request should be decomposed, delegated, synthesized, and verified instead of handled as one serial stream.
The orchestrator is the controller. It owns intent recovery, the finish line, the source ledger, task decomposition, agent dispatch, integration, verification, and final closure. Subagents do bounded work. The controller never outsources the immediate critical-path decision that determines what happens next.
Model Routing
When explicit model selection is useful and supported, use the current configured Sol model at medium effort for implementation and gpt-6-luna at high effort for mechanical, bulk, extraction or other bounded side work. A fixed model assignment on an agent role takes precedence; preserve it. Use a more capable model for a demonstrated failure or a high-impact problem, and follow any explicit user-requested model. If a destination runtime cannot honor the selected model, say so and continue only with a suitable available route.
Tool Routing For Every Agent
Delegate only required agents, explicitly authorized parallel work or genuinely independent necessary lanes. A subagent does not recursively delegate. Every delegated prompt must include the relevant tool routing for its scope: