dev-reviewlisted

Code-focused plan-bounce-execute workflow between Claude Code (Opus) and Codex CLI. Use when the user wants repo files changed, a bug fixed, a feature implemented, or a code plan verified before execution. One AI composes a plan, it bounces between agents with [CONTESTED]/[CLARIFY] markers until refined, then the designated agent executes the code. Replaces manual copy-paste between Claude Code and Codex desktops. Triggers on "dev review", "dev-review", "code review loop", "plan then execute", "have codex implement", "have codex review this diff", "developer reviewer loop", "compose execute verify", and explicit /dev-review requests. Generic co-evolution, bounce, cross-AI refinement, document refinement, and stress-test requests should use /co-evolution instead.
alanshurafa/co-evolution · ★ 4 · AI & Automation · score 73

Install: claude install-skill alanshurafa/co-evolution

# /dev-review - Plan-Bounce-Execute Workflow Automates the workflow of composing a code plan with one AI, bouncing it between agents for refinement using [CONTESTED]/[CLARIFY] markers, then having one agent execute the final plan into code. Replaces manual copy-paste between Claude Code and Codex. Use `/co-evolution` for general questions, ideas, arguments, prompt refinement, or document bounces. Use `/dev-review` only when the intended deliverable is a repo change or code-focused verification workflow. For the **detached** flavor — the session plans and reviews while Codex executes in the background and the session is woken at gates instead of babysitting — use `/codex-build` (`skills/codex-build/`). It kicks the standalone runner with `--preset codex-build` (Opus plans at `high`, Codex executes at `xhigh`, Opus reviews at `max`; `--verify` on, bounces `2`, revise-loop `1`) and applies a schema-bound ACCEPT / REVISE / ESCALATE gate. `/dev-review` is the interactive single-session loop; `/codex-build` is the same pipeline run detached. When `--live` is enabled on Windows, each Codex pass runs in a visible PowerShell window so the user can watch progress in real time. The handoff contract stays file-based: prompts are written to disk, Codex writes the final message to disk, and Claude Code reads the resulting artifact before continuing. The workflow has three phases: 1. **Compose** - One agent creates the initial plan/approach 2. **Bounce** - The plan document bounces bet