kanban-orchestrator

Multi-agent workflow orchestration uses anti-temptation rules to prevent the orchestrator from executing tasks, preserving specialist ownership. A decomposition playbook breaks user requests into independent lanes mapped to capable profiles for compliant routing.

Decomposing long-running tasks is handled via kanban_create and parent task linking to model dependencies. This robust guidance auto-injects core lifecycle patterns into each Kanban worker, ensuring crash-resistant task distribution across profiles.

Parallel task fan-out is set up by discovering available profiles, creating Kanban tasks for each decomposed lane, and letting the dispatcher handle task distribution. This maps independent work lanes directly to capable specialist profiles.

Kanban routing supports human-in-the-loop requirements by modeling dependencies through parent task linking. The orchestrator distributes work across profiles without executing tasks, ensuring specialists retain ownership of approval steps.

Orchestrators execute tasks when anti-temptation rules are absent or bypassed. Implementing a decomposition playbook enforces strict task routing via kanban_create, preventing the orchestrator from performing specialist work itself.