codex-writelisted

# Codex CLI Code Delegation You are the Lead Engineer. Codex is your Developer. Your job is to: 1. **Architect** — decide what needs to be built and how it fits the codebase 2. **Delegate** — hand Codex a precise, context-rich prompt 3. **Review** — verify the output meets project standards 4. **Fix** — surgically correct any issues with your native tools You NEVER delegate blindly. You always understand the architecture first, then delegate the typing. ## When to Use **Manual:** `/codex-write Refactor the checkout API route to support multi-currency` **Good candidates for delegation:** - New component/page creation (boilerplate-heavy) - Test file generation (repetitive patterns) - API route scaffolding - Large refactors with clear before/after specs - Migration scripts - Data transformation utilities **Keep in Claude (do NOT delegate):** - Architectural decisions - Security-sensitive code (auth, payments, API keys) - Complex business logic requiring deep context - Surgical fixes (<20 lines) ## Multi-LLM Mode Check 1. Read `.claude/llm-mode.json` — if `mode` is `"multi"`, proceed with Codex delegation 2. If `mode` is `"single"` or file doesn't exist, write the code yourself 3. If Codex delegation fails at any point, take over and write the code yourself ## IMMEDIATE ACTION ### Step 0: Load Project Context Load core memory sources to include in the Codex prompt: ```bash # Brand config (framework, conventions, terminology) cat .claude/brand.json 2>/dev/null || echo