kanban-orchestrator

To orchestrate multi-agent workflows safely, you decompose complex requests into Kanban task graphs and route each workstream to appropriate worker profiles. This enforces a decompose-don't-execute rule, ensuring the orchestrator only manages task routing and dependency gating while specialists handle implementation.

Profile-aware task decomposition is the process of discovering which worker profiles exist before assigning work, preventing silent failures from unknown assignees. It splits requests into parallel Kanban lanes and creates dependent cards with valid assignee selection and parent-linked task creation.

You set up dependency gating by creating Kanban cards with proper parent links that block downstream work until completion. This supports synthesis, review, and human-in-the-loop handoff patterns, generating completion or blocking summaries that preserve the audit trail across multi-agent setups.

Yes, task routing supports goal-mode and recovery for long-running workflows. The orchestration maintains an audit trail through blocking summaries and parent-linked task creation, helping avoid over-linking or bundling unrelated work while keeping dependent workstreams moving.

The primary limitation is that the orchestrator cannot execute implementation itself, requiring valid available profiles for every assignee. It also requires careful dependency management to avoid over-linking unrelated work, meaning requests without clear specialist profiles will fail during task routing.

Yes, you need existing worker profiles before assigning Kanban tasks. The orchestrator discovers which profiles actually exist before routing work to prevent silent failures from unknown assignees, ensuring every parent-linked task card has a valid specialist for implementation.