kanban-orchestrator

Multi-agent orchestration routes work by decomposing goals into a Kanban task graph with parent-child dependencies and gating, ensuring specialist routing stays consistent and preserves an audit trail.

Task decomposition breaks ambiguous goals into a Kanban lifecycle: understand objectives, sketch a task graph, create linked tasks with dependency gates, and summarize results for human-in-the-loop review.

Anti-temptation safeguards enforce a strict decompose, route, and summarize playbook, preventing the orchestrator from executing work directly and providing reassignment guidance for reviewer-needed changes.

Yes, workflow planning uses consistent specialist-roster conventions for research, analysis, writing, reviewing, engineering, ops, and PM roles, ensuring routing survives restarts and supports iterative interventions.

Yes, multi-agent orchestration applies to iterative workflows by maintaining a persistent Kanban board with dependency gating, which supports human-in-the-loop interventions and preserves task state across restarts.