claude-implementlisted

# Delegate implementation to headless Claude, then verify Claude as the implementation leg. From a codex or agy lead this is the primary way to put the Claude family on the implementer side; from a Claude lead, prefer in-session subagents unless the delegate genuinely needs its own working directory, permission mode, or model (runtime file). ## Before the first run of a session Read **[`../claude-adversarial-review/references/claude-runtime.md`](../claude-adversarial-review/references/claude-runtime.md)** — the invocation shapes, measured `acceptEdits` behavior, patience calibration, and the instruction-layer inheritance property are there and assumed here. ## Worktree, always ```bash BASE=$(git rev-parse HEAD) # from a clean checkout, recorded before anything git worktree add -b claude/<short-task-slug> ../<repo>-claude-<short-task-slug> "$BASE" ``` Verify against that exact SHA later — never against a moving branch name. ## Run it ```bash RUN_DIR=$(mktemp -d "${TMPDIR:-/tmp}/claude-implement.XXXXXX") # Write the task prompt to "$RUN_DIR/task.md" in its own step. cd "$WORKTREE" && claude -p "$(cat "$RUN_DIR/task.md")" \ --permission-mode acceptEdits --model <tier> \ > "$RUN_DIR/impl.out" 2>&1 ``` Measured properties of this exact shape (runtime file has the detail): `acceptEdits` covers file writes and shell/git in one flag — it can `git add`, `git commit`, and **run the repo's test suite natively** (no pinned spellings, contrast agy); the working directory i