Claude Codex Orchestrator — Development skill for Claude Code

claude-codex-orchestrator

**Claude plans and verifies. Luna handles most bounded execution, Terra handles implementation judgment, and Sol handles the toughest work.**

  


Why

Claude is the orchestrator and accepting judge. Codex is the execution surface. The router spends the narrowest capable model on each frozen packet:

• Luna Max for most fully specified, deterministic implementation;
• Luna Max Fast when latency materially matters;
• Terra High when localized implementation judgment remains;
• Sol High for architecture-sensitive, security, contract, concurrency, or other highest-risk work;
• Sol review/rescue for read-only review and stuck-task diagnosis.

Unresolved product and architecture decisions stay with Claude, as does final verification.

The loop

1. Plan — Claude resolves intent and decomposes the work.
2. Preflight — each cold packet is decision-complete and at most 12 KiB; source stays in the worktree and is referenced by path and symbol.
3. Dispatch — invoke one direct profile, or use the opt-in Sol-led orchestrated profile for a large frozen work order.
4. Execute — Luna routes to Terra when a decision appears; Terra routes to Sol at a high-risk boundary.
5. Review and verify — Codex may provide a read-only first review, but Claude inspects the diff and reruns the proof before accepting it.

The bounded packet preflight prevents the repeated oversized handoff and guessed chunk-size loop reported in [issue #6](https://github.com/vimoxshah/claude-codex-orchestrator/issues/6).

Direct profiles

Profile	Model and effort	Tier	Use
luna-worker	gpt-5.6-luna max	default	D