kanban-orchestrator

Multi-step work is split by routing the request into a Kanban task graph, creating parallel cards for independent work and parent-linked cards for gated dependencies to keep execution synchronized across available profiles.

Multi-agent orchestration is managed by decomposing mixed requests into research, implementation, synthesis, and review lanes, then assigning each card to a discovered worker profile instead of having the orchestrator execute the work itself.

Worker assignment requires discovering which profiles actually exist first, then using explicit assignee names when creating Kanban cards to route specialized tasks safely to the correct specialist.

Stuck workers are recovered cautiously through reclaim, reassign, or model changes while preserving auditability and keeping parent-linked tasks synchronized in the correct namespace.

Kanban task graphs support human-in-the-loop workflows by applying dependency-safe fan-out to planning, research, implementation, review, and validation tasks that require gated execution across multiple profiles.

Multi-agent task routing should be avoided for simple, single-step requests that do not require discovery, decomposition, and coordination across multiple worker profiles or parallel dependency gates.