
from hermes-one-click139
Guidelines and workflow for running Codex as an isolated implementation lane while Hermes retains Kanban ownership, verification, and handoff.
Defines a safe, repeatable convention for Hermes workers to spawn Codex as an isolated implementation lane: create a separate worktree/branch, run Codex to produce diffs or commits, and then reconcile and verify changes under Hermes control. The skill provides ownership rules, monitoring/kill conditions, and a reconciliation checklist to ensure safety and test verification.
Use when a Kanban task is a bounded coding/refactor/documentation job with clear acceptance criteria and when changes can be evaluated by Hermes. Do NOT use for tasks that require human judgment, touch secrets, or are safety-sensitive without extra review.
Designed for Hermes-style orchestrators working with Codex or similar code-writing agents (Codex CLI, Copilot-assisted workflows). Requires shell/git access and the ability to run verification scripts.
Kanban Codex Lane defines a dual-lane convention for Hermes workers to delegate implementation work to Codex CLI in isolated git worktrees. It has thorough ownership rules, safety constraints, reconciliation checklists, and a well-defined metadata schema. No scripts were bundled. The skill is niche — it targets a specific Hermes+Codex workflow for prediction-market-bot repos, limiting broad applicability.
Well-structured skill with clear security boundaries: Codex is never trusted as an owner, must run in isolated worktrees, and Hermes always retains lifecycle control. No exfiltration risks, no hardcoded credentials, no destructive commands without guards. The git worktree cleanup uses branch deletion only after accepted commits are preserved. Shell variable quoting is proper (uses double quotes around $REPO, etc.). The skill is highly specific to the Hermes+Codex+prediction-market-bot ecosystem, which limits its usefulness score.