Codex Mission Control

Act as a thin manager for a larger Codex mission. Keep this thread focused on decisions, routing, status, and final integration. Move deep exploration, long logs, and bounded implementation slices into focused subagents or separate Codex threads when the user has authorized that style of execution.

Core Model

1. The manager owns the mission goal, constraints, workstream map, handoffs, thread registry, integration, and final answer.
2. Subagents are best for parallel, bounded work inside the current turn.
3. Separate Codex threads are best for context isolation, longer work, different branches, different worktrees, or multi turn follow up.
4. Every mission must use a run scoped ledger path, never one global shared filename (see Gotchas item 2).
5. Every worker must return a compact report per the Worker Prompt Pattern.
6. This skill is an orchestration workflow. It must discover and use host tools for subagents; it cannot create workers merely by describing them.

First Move