kanban-orchestrator

Kanban task decomposition breaks down complex objectives into parent-child task graphs using kanban_create, enforcing dependency gating so subtasks route to specialists instead of executing directly. This creates a persistent audit trail for recovery.

Multi-agent routing assigns decomposed Kanban subtasks to a standard specialist roster including researcher, analyst, writer, reviewer, backend-eng, frontend-eng, ops, and pm roles. Anti-temptation guardrails enforce task routing instead of direct execution.

Use persistent Kanban work plans for multi-step research, drafting, review gating, and parallel execution scenarios. They provide an audit trail and enable crash recovery when orchestrating complex objectives that require dependency management.

Yes, kanban-orchestrator supports parallel execution and review gating scenarios by decomposing objectives into a persistent task graph with parent gating, routing subtasks to specialist profiles while maintaining recovery and audit capabilities.

When a specialist profile is missing from the roster, anti-temptation guardrails enforce asking the user to define the missing profile rather than allowing the agent to execute the routed task directly.

Kanban orchestration requires defining specialist profiles upfront and relies on dependency gating, meaning tasks cannot execute directly. If a profile is undefined, the workflow pauses to request user input rather than auto-resolving the gap.