kanban-codex-lane

Automates Codex-assisted implementation in isolated temporary worktrees for Cronus Kanban workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/matlee0409/cronus --skill kanban-codex-lane-matlee0409
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kanban-codex-lane
Source: https://github.com/matlee0409/cronus/tree/main/skills/autonomous-ai-agents/kanban-codex-lane
Command: npx skills add https://github.com/matlee0409/cronus --skill kanban-codex-lane-matlee0409

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cronus Kanban workers often need bounded, isolated help from Codex for implementation tasks without relinquishing control over lifecycle, reproducibility, and safety. This skill defines the lightweight Codex lane that Cronus can spawn inside an isolated worktree to draft changes, reconcile results, and hand off with Cronus ownership intact.

Core Features & Use Cases

  • Isolated worktree execution: Codex runs in a temporary, branch-scoped environment to prevent changes leaking into the main workflow.
  • Lifecycle ownership: Cronus retains task ownership, reviews diffs, and applies accepted commits after verification.
  • Structured handoff and reconciliation: Reconciles Codex output, runs tests, and writes kanban_complete or kanban_block signals.

Quick Start

Launch the Codex lane in an isolated worktree for your Kanban task and review the resulting diffs, tests, and handoff artifacts.

Frequently Asked Questions about kanban-codex-lane

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I isolate Codex code changes in a temporary worktree for Kanban tasks?

To isolate Codex changes for Kanban tasks, you spawn a lightweight Codex lane inside a branch-scoped, temporary worktree. This prevents drafts from leaking into the main workflow while maintaining reproducible, bounded execution.

What is the best way to retain lifecycle ownership when using Codex for refactoring?

Retaining lifecycle ownership during Codex refactoring means Cronus acts as the primary worker, reviewing diffs and applying accepted commits only after test verification, ensuring the automated assistant never takes control of the task lifecycle.

How do I reconcile Codex outputs and verify tests before committing?

You reconcile Codex outputs by reviewing the generated diffs, running test verification within the isolated environment, and writing kanban_complete or kanban_block signals to document the handoff state before final application.

Can I use a Kanban workflow to manage small commits and branch naming for Codex drafts?

Yes, you can use a Kanban workflow to enforce small commits, specific branch naming, and strict safety constraints for Codex drafts. The workflow manages these requirements natively within the temporary worktree execution.

Does isolated worktree execution work for bounded documentation tasks?

Isolated worktree execution works effectively for bounded documentation tasks by providing a safe, temporary environment. Codex proposes draft changes that Cronus can review and apply without risking the main project state.