# Clodex Workflow

> Use when coordinating Claude Code CLI planning with Codex CLI implementation and dual adversarial audit.

- Skill: `dasblueyeddevil/clodex-workflow` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dasblueyeddevil/clodex-workflow`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dasblueyeddevil/clodex-workflow/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: DasBluEyedDevil (https://skillmd.com/u/dasblueyeddevil)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/dasblueyeddevil/clodex-workflow

---


# Clodex Workflow

Prefer native Clodex coordination when the repository has been initialized with
`clodex init`: use the available MCP handoff tools first, and use
`clodex task ...`, `clodex audit --diff`, and `clodex status` as fallbacks. The
older harness commands remain valid for scripted or non-MCP workflows.

Harness commands:

1. `clodex plan "<task>"` asks Claude Code CLI to produce a structured plan.
2. `clodex build "<task>"` runs Claude planning, Codex implementation, and multi-reviewer audit in an isolated worktree.
3. `clodex apply <run-id>` applies an approved worktree patch back to the source checkout.
4. `clodex task start/get/cancel/list` manages durable async runs.
5. `clodex audit --diff` audits the current uncommitted diff with both Claude and Codex.
6. `clodex status` shows recent local task and run state.

Defaults:

- Claude planner/auditor: `claude -p --model opus --effort max --permission-mode plan`.
- Codex engineer/auditor: `codex exec` or `codex review` with `gpt-5.5` and `model_reasoning_effort="xhigh"`.
- Builds default to `.clodex/workspaces/<run-id>/`; use `--workspace local` only when in-place changes are intentional.
- Approval profiles are `ci`, `local`, and `auto_review`; `ci` is the deterministic default.
- Subscription CLI auth is preferred. API keys are fallback-only for CI/headless use.

Do not mark a run complete unless `.clodex/runs/<run-id>/05-agreement.json`
contains `approved: true`.