kanban-orchestrator

Kanban task decomposition routes a complex goal into a parallel workstream graph, assigning each lane to the appropriate Hermes profile via Kanban cards instead of executing the work directly. It enforces an orchestration-only guardrail to prevent premature execution.

Multi-agent routing maps decomposed workstreams to specific Hermes profiles, enabling fan-out research workflows and gated synthesis steps. It links tasks with correct parent dependencies and uses crash-safe persistence via Kanban rows to track the entire workflow.

To set up Kanban orchestration, first discover available Hermes profiles locally to prevent routing failures. Then define the user goal, approve the generated task graph, and use kanban_create to generate assigned cards with correct parent dependencies for each specialist.

Profile discovery happens automatically before planning to ensure routing does not silently fail on unknown assignees. The orchestrator checks which Hermes profiles exist locally, maps workstreams to them, and then creates the dependent Kanban tasks.

An orchestrator executes work directly when anti-temptation guardrails are missing. This Skill enforces a decompose-don't-execute rule by ensuring every concrete action becomes an assigned Kanban card routed to a specialist, preventing the system from doing the work itself.

Yes, Kanban orchestration applies to scenarios with parallel lanes, fan-out/fan-in research workflows, and gated synthesis or review steps. It creates tasks with correct parent dependencies to ensure review gates are respected before downstream synthesis begins.