kanban-batch-run

Batch-run kanban orchestration sequences multiple tasks in planned order using selectors like 500-504, invoking the inner kanban-run workflow to execute ordered task lists automatically with conservative sequencing and controlled parallelism.

Batch kanban execution resolves dependencies and forms task groups before invocation, applying safety checks and conservative sequencing to maintain visibility and safety while improving throughput across the planned batch.

Batch kanban orchestration supports resume points and offers automatic versus user-confirmed execution modes, allowing you to accommodate risk and recover from failures during end-to-end task sequencing.

Using a batch selector like 500-504 is the best way to execute short ordered task lists, as it expands selectors, orders tasks by phase, and orchestrates task-level invocations deterministically.

Yes, batch kanban orchestration builds directly upon existing kanban and kanban-run workflows, utilizing a codex fallback to slash commands when needed to invoke the inner kanban-run skill safely.

You should avoid automatic batch execution for kanban tasks when risk levels are high; instead, use the user-confirmed execution mode to manually approve each step in the planned batch sequence.