Skill · Agent Orchestration
Orchestrate
Coordinate focused subagents on substantial work, keep their ownership non-overlapping, and integrate verified results. Use for large-scope Codex tasks; keep trivial work with the coordinator.
How to use it
- Start your plan and connect your AI once
- Ask for the task in your own words, or say it directly:
Use the Orchestrate skill to help me with this.Without a connection: copy the SKILL.md below into your AI's project instructions.
Orchestrate
Coordinate substantial work across focused subagents while remaining available to the user and retaining responsibility for the integrated result.
When to Use
- Use when a task has multiple independent research, review, or implementation lanes.
- Use when parallel work will materially reduce elapsed time or improve coverage.
- Use when a coordinator must synthesize several bounded outputs into one verified result.
Keep trivial tasks with the coordinator.
Workflow
- Decompose the task into distinct, bounded assignments with explicit outputs.
- Run narrow, read-only scouts in parallel with low reasoning effort and no
- Use medium reasoning effort for routine implementation and high reasoning
- Give each subagent distinct ownership. Prevent overlapping assignments, and
- Integrate the outputs, resolve conflicts, and verify the combined result.
- Keep approvals and externally consequential decisions with the user.
inherited conversation when the runtime supports those controls. Give each scout all scoped context and evidence required to complete its assignment.
effort for difficult work.
instruct leaf workers not to delegate.
Examples
- For a repository-wide feature, assign non-overlapping agents to architecture
- For a research brief, assign independent sources or questions to read-only
inspection, implementation, and test review, then integrate their findings and run the final verification from the coordinator.
scouts, reconcile disagreements, and keep the final judgment with the coordinator.
Limitations
- Requires a runtime that exposes subagent or delegation tools; otherwise keep
- Delegation does not authorize file mutations, public actions, purchases, or
- Parallel agents can add cost and coordination overhead, so use them only when
- The coordinator remains responsible for checking claims, changes, tests, and
the work with the coordinator.
other consequential operations beyond the user's original scope.
the task is substantial enough to benefit.
the final answer.