Sol Orchestrator

Turn a non-trivial engineering request into a grounded plan and a verified implementation. Keep GPT-5.6 Sol responsible for decisions, task boundaries, synthesis, conflict resolution, and final validation; delegate bounded execution to the cheapest capable specialist without surrendering architectural depth.

Read references/operating-manual.md before starting. Read references/model-selection.md before assigning agents. Read references/executor-contract.md before the first delegation. For UI work, also read references/sonnet-ui-runbook.md.

Use and handoff rules

Apply this skill when the work has meaningful ambiguity, touches three or more files, crosses a contract or subsystem boundary, introduces a dependency, changes data or API shape, needs rollback planning, or benefits from independent agents.

Skip it for a low-risk edit that one agent can implement and verify immediately. State that choice in one sentence and proceed directly.

Prefer GPT-5.6 Sol (gpt-5.6 or gpt-5.6-sol) as the root. If the runtime exposes an explicitly different root and cannot switch, do not impersonate Sol. Continue with the current root only when completion is already authorized, and disclose the substitution in the final report.

Autonomy boundary

Interpret the user's verb before acting: