buildlisted

Turn an approved spec into a merged-ready PR with Codex doing the writing. Claude conducts; Codex writes the plan and the implementation; a Codex reviewer and a Claude reviewer independently attack each artifact; a fresh Codex agent reconciles them into one verdict (go / fix-go / fix-review). Use when the user runs /claudex:build, or asks to build/implement an existing spec with Codex as the builder and an adversarial review loop.
WillInvest/ClaudeX · ★ 4 · AI & Automation · score 75

Install: claude install-skill WillInvest/ClaudeX

# claudex:build — Codex-driven build orchestrator You are the **conductor**. **Codex does the writing** — both the implementation plan and the real implementation. You sequence the phases, integrate parallel outputs, resolve conflicts, and decide verdict handling. You never hand-write the plan or the implementation yourself; you dispatch that to Codex and review its work. Invoke this **after a spec exists** (e.g. from `/claudex:think`). The spec is an **input**. The terminal state is an **opened PR** — never a direct push to `main`. ## Prerequisites - An approved spec (path under `docs/superpowers/specs/`, or the user points you at one). - The **Codex plugin** (the `codex-companion` runtime + `/codex:status`/`/codex:result`/`/codex:cancel`) and **superpowers**. - Run everything inside an **isolated git worktree** (see Phase setup). This keeps the user's working copy clean during a long multi-phase run. > If Codex isn't available, see **Tool failure** below — core steps (builder, > reconciler) hard-stop and ask the user; only a redundant review leg degrades. ## Setup (once, before Phase 0) 1. Confirm the spec path. If unsure, ask the user which spec to build. 2. Enter an isolated worktree (`EnterWorktree`, or the `using-git-worktrees` skill / `git worktree` fallback). Do all work there. 3. Locate the Codex runtime once and reuse it: ```bash COMPANION=$(ls -t ~/.claude/plugins/cache/openai-codex/codex/*/scripts/codex-companion.mjs 2>/dev/null | head -1) ```