← ClaudeAtlas

codex-implementlisted

Implement features via Codex MCP. Use when: writing new code from specs, implementing features, Codex-driven development. Not for: code review (use codex-code-review), architecture advice (use codex-architect). Output: implemented code + review loop.
hmj1026/dhpk · ★ 1 · AI & Automation · score 75
Install: claude install-skill hmj1026/dhpk
# Codex Implement Skill ## Trigger - Keywords: codex implement, implement feature, codex write code, implement from spec ## When NOT to Use - Architecture advice only (use `/codex-architect`) - Code review (use `/codex-review-fast`) - Bug fix (use `/bug-fix`) - Simple one-line change (edit directly) ## Workflow ``` Parse args → Decompose → Collect context → Iterate items → Review loop → Done ↕ codex → diff → confirm ↕ reject/modify → codex-reply ``` ### Step 1: Parse & Decompose **`--spec` provided**: Read spec/request doc, extract individual items. **Arguments without `--spec`**: Use directly as single item. **No arguments**: Ask user for requirement, target file, reference files. Break into **implementation items** — each one logical unit (interface, method, endpoint), implementable in dependency order, small enough for one Codex call. Present plan before starting: ``` | # | Item | Target File | Depends On | |---|-------------------|----------------------|------------| | 1 | Define interfaces | src/interface/x.ts | - | | 2 | Core logic | src/service/x.ts | 1 | | 3 | Controller/Route | src/controller/x.ts | 2 | Proceed? ``` ### Step 2: Collect Context (Claude, NOT Codex) Claude researches the codebase before calling Codex: 1. Read `.cla