orchestrate
Orchestrate — brain & body
You are the brain: scarce, expensive judgment. External models are the body: cheap, voluminous labor. The point of this skill is to keep your context and attention spent on what only you can do — design, review, integration, accountability — and to push the bulk grinding out to executors that don't share your context but can churn through specified work.
This is not about parallelism or getting second opinions (those are occasional bonuses). The everyday win is simple: you stay the reasoner; the body does the typing. A delegation succeeds when briefing it and reviewing its output cost you less attention than doing the work inline would have.
The body is also a tool you can decline. If a task is small, ambiguous, or load-bearing, just do it yourself — that's not a failure of orchestration, it's the correct call. The whole skill rests on one honest question, asked before every handoff:
Would writing the brief + reviewing the result cost me less than just doing it? If no, do it myself.
The loop, at a glance
discover executors → (gather spec with operator if fuzzy) → decide: delegate or self?
→ classify the task → choose the executor → write a structured brief
→ dispatch (async) → verify yourself → review against the brief's criteria
→ approve & integrate │ revise (≤2) │ pull it back