kanban-orchestrator

Multi-step requests are decomposed into Kanban tasks by routing the work into parallel lanes and creating dependent follow-up cards, preventing the AI from executing complex work all at once. This ensures work moves in the correct order.

Dependency-aware task routing uses strict parent-child task linking to map task graphs, ensuring synthesis, review, and integration steps do not start until their upstream dependencies are fully resolved. This maintains safe execution order.

Yes, profile discovery is required to identify which worker profiles actually exist before assigning work. Mapping each lane to a real assignee ensures that routed Kanban tasks are allocated to valid, available workers.

Fan-out and fan-in coordination is handled by splitting requests into parallel lanes and creating dependent follow-up cards with strict parent-child links. This orchestrates the task graph so integration steps wait for parallel work to finish.

Kanban orchestration supports recovery-safe completion behavior, allowing complex work routed into dependent Kanban lanes to resume correctly if interrupted. Parent-child task linking ensures the task graph state is preserved.

Use a Kanban orchestrator instead of an executor when a request requires planning, decomposition, and multi-step coordination. It maps lanes and creates dependency-aware cards so the work moves in the right order rather than executing all at once.