kanban-orchestrator

Kanban task graph decomposition starts by clarifying ambiguous goals, sketching a dependency-gated task plan, and creating parent/child tasks with assignees. This enforces controlled promotion and routes work to specialists instead of the orchestrator executing it.

Dependency gating in a multi-agent Kanban workflow uses parent and child task relationships to enforce controlled promotion. It prevents downstream specialists from starting work until upstream tasks are completed and summarized via kanban_complete actions.

Kanban workflow recovery involves reclaiming, reassigning, or changing the model of stuck specialist workers. These operational actions handle crashes, hallucinations, and blocked states to resume the dependency-gated task graph.

The Kanban orchestrator does not execute specialist tasks itself. It enforces a strict route-don't-execute policy, acting only to create Kanban tasks with assignees and parents, preventing the orchestrator from taking over implementation.

You can use a standard specialist roster including researcher, analyst, writer, reviewer, backend/front-end engineers, ops, and pm roles. These workspace conventions keep fan-out research, synthesis, drafting, and review consistent across the Kanban workflow.

Kanban decomposition workflows require predefined task graph planning and strict dependency gating. Without proper kanban_create and kanban_complete summaries, the persistent audit trace breaks, and recovery actions are needed when workers crash or hallucinate.