kanban-orchestrator

To decompose a multi-lane request into a routed Kanban task graph, the orchestrator breaks the request into concrete work items, creates Kanban cards for each, and routes them to the correct specialist profiles without executing the work directly.

The best way to orchestrate parallel fan-out and fan-in workflows is by creating independent ready cards for parallel lanes and using parent links to ensure child tasks only start after required inputs finish.

Profile-grounded task decomposition prevents silent routing failures by discovering which assignee profiles actually exist on your machine before planning, ensuring concrete work items route to valid specialists.

Yes, you can use Kanban orchestration for human-in-the-loop review and iteration cycles by creating blocking and unblocking patterns within the task graph to pause work until manual review is complete.

The orchestrator enforces a decompose, don't execute rule to prevent the model from prematurely executing work, ensuring it instead creates every concrete work item as a Kanban card and reports the task structure back.

To recover a multi-agent pipeline when workers get stuck, the orchestrator provides recovery-aware operations that guide how to reclaim, reassign, or adjust profile model settings for misconfigured workers.