← ClaudeAtlas

codex-claude-handofflisted

Run the project-local Codex to Claude Code to Codex handoff protocol. Use only when the user selects codex-claude-handoff through /skills, mentions $codex-claude-handoff, names codex-claude-handoff, or explicitly requests the full Codex-Claude handoff protocol; do not trigger for ordinary project tasks.
siglernir-ai/codex-claude-handoff · ★ 0 · AI & Automation · score 72
Install: claude install-skill siglernir-ai/codex-claude-handoff
# Codex-Claude Handoff Skill ## Purpose Use this skill to coordinate AI tools in the same software project using a shared handoff file (`AI_HANDOFF.md`) as the execution state. ## Recommended Workspace The recommended user-facing workspace is VS Code with the same project folder open for Codex and Claude Code. The tools coordinate through the project's local handoff files, not through a hidden chat bridge. VS Code is a convenient shared workspace; this protocol does not install a VS Code extension or provide unrestricted background automation. When a window turn is manual, `NEXT_TURN.md` contains the short prompt for the next tool. Bounded CLI automation is available only for the states and adapters documented in `ADAPTERS.md`, and sensitive actions still require the user. ## Role Model The protocol is organized around three roles, plus the User. Roles are bound to concrete tools in `.ai/roles/ROLE_ASSIGNMENT.md`, so they can be reassigned (with user approval) without rewriting the protocol. - **Master** - decision router, architect, task writer, and coordinator. - **Implementer** - implementation agent; during investigation and planning turns also a read-only repository-local feasibility and capability partner. - **Reviewer** - independent review of implementation against approved scope, plus the Verification Gate. - **The User** - the approval point. Never one of the three roles. **Default binding:** Master = Codex, Reviewer = Codex, Implementer = Claude Code. This