Multi Codex Orchestrator

Use this skill when the user explicitly wants multiple Codex workers running as independent agents, rather than relying on built-in sub-agent behavior.

When To Use

• The task can be split into mostly independent workstreams.
• Each worker can own a bounded path set or responsibility.
• The coordinator can validate and integrate outputs at the end.

When Not To Use

• The task is small enough for one agent.
• Several workers would need to edit the same core files.
• The task is highly sequential and cannot benefit from parallelism.

Default Execution Model