Kanban Codex Lane

Overview

This skill defines the lightweight Hermes+Codex dual-lane convention for Kanban workers. Hermes is always the task owner: it calls kanban_show, decides whether Codex is appropriate, creates or selects an isolated workspace, starts and monitors Codex, reconciles any diff, runs verification, and writes the final kanban_complete or kanban_block handoff. Codex is an input lane only. Codex output is not a task completion signal, not a trusted reviewer, and not allowed to write durable Kanban state directly.

The convention exists so a Hermes worker can use Codex for bounded implementation help without changing the dispatcher. The dispatcher must still spawn Hermes workers. A worker may optionally spawn Codex inside its own run, then accept, partially accept, or reject the lane after independent review and tests.

When to Use

Use the Codex lane when all of these are true:

• The Kanban task is a coding, refactor, documentation, test, or mechanical migration task with clear acceptance criteria.
• A bounded diff can be evaluated by Hermes in one run.
• The repo can be copied or checked out in an isolated git worktree/branch.
• Hermes can run the relevant tests itself after Codex exits.
• The prompt can state all safety constraints and files that must not change.

Do not use the Codex lane when any of these are true: