Orchestrating agent delegation

The general delegation mechanics — briefs, model tiering, verification — for the orchestrator agent (the "CTO layer") that stays in the judgment layer while subagents execute.

When to use

• Dispatching subagents to non-trivial work.
• Writing a prompt for an agent that will do the coding.
• Planning parallel work across agents.
• Structuring an adversarial review panel.
• Reviewing a draft prompt before it is sent.

When NOT to use

• Single-shot trivial tasks (typo fix, one-line rename) — direct action beats delegation overhead.
• When you are the executing agent, not the orchestrator — this skill is the layer above.
• Solo work where no delegation is planned.

Core principles