kanban-orchestrator

Multi-agent orchestration routes work by decomposing a goal into a Kanban task graph, assigning each workstream to a specialist profile, and using parent links to gate dependencies without executing the tasks directly.

Profile-aware decomposition routes parallel workstreams by discovering available Hermes profiles first, creating independent cards for separate lanes, and using parents=[...] to enforce dependency promotion for review-gated pipelines.

Dependency-correct workflow planning sets up fan-out and fan-in by creating parallel cards with no parent links for independent lanes, using parents=[...] to ensure synthesis or review tasks cannot run until required inputs complete.

An orchestrator executes tasks directly when lacking anti-temptation guardrails; enforcing decompose, don’t execute rules turns concrete work into assigned Kanban tasks routed to real existing profiles, preventing direct execution.

No, profile-aware decomposition requires discovering available Hermes profiles before planning, ensuring each workstream routes to an existing assignee and avoiding made-up profile names that would silently fail during task routing.

A limitation of using parent links for dependency graphs is that independent lanes must be created as parallel cards with no parent links; otherwise, you incorrectly enforce sequential execution on workstreams that should run simultaneously.