codex-ctolisted

# Codex CTO — Inverted Orchestration Codex plans and reviews. Claude Code executes. This inverts the `codex-orchestrator` pattern: instead of Claude Code delegating to Codex subagents, Codex directs Claude Code as the engineering team. ## Protocol ``` 1. CTO plans → cto-invoke.sh plan "<objective>" 2. You execute → native tools (Read, Edit, Write, Bash, Glob, Grep) 3. CTO reviews → cto-invoke.sh review "<objective + results>" 4. Loop → if "revise", fix and re-submit for review (max 5 iterations) ``` ## Step 1: Get the Plan Run the plan phase with the user's objective: ```bash ~/.claude/skills/codex-cto/scripts/cto-invoke.sh plan "<OBJECTIVE>" [--model MODEL] ``` Parse the returned JSON. It contains: - `objective` — what to accomplish - `analysis` — CTO's assessment of the codebase - `strategy` — high-level approach - `tasks[]` — ordered task list with IDs, actions, targets, descriptions, acceptance criteria, and dependencies - `verification` — commands to run after all tasks complete ## Step 2: Execute Tasks Work through each task in dependency order using native tools. For each task: 1. Read the `description` and `acceptance_criteria` 2. Execute the action (`create_file`, `modify_file`, `delete_file`, `run_command`, `verify`) 3. Verify each acceptance criterion before moving to the next task 4. Track what was done and what the outcome was Do not deviate from the plan without reason. If a task is blocked or the plan has an error, note it and continu