kanban-orchestrator

Multi-agent orchestration requires enforcing anti-temptation guardrails that route work into specialist tasks. The Skill decomposes goals into a Kanban task graph, forcing the orchestrator to assign concrete tasks rather than self-executing them.

Task dependency management uses parent-child links and gating to control readiness. Downstream tasks remain blocked until prerequisite tasks complete, enabling fan-out and fan-in patterns for parallel research, synthesis, drafting, and review workflows.

Project decomposition starts by defining a task graph before creating anything. You route work to specialist profiles like researcher, analyst, writer, and reviewer, ensuring outputs chain correctly through dependency gating and human-in-the-loop checkpoints.

Human-in-the-loop checkpoints integrate directly with parallel task routing. The Skill applies gating via parent-child links, allowing human review before downstream tasks promote to ready, ensuring quality control across specialist task chains.

Specialist roster conventions route tasks to predefined profiles such as researcher, analyst, writer, reviewer, backend, front-end, ops, and pm. This ensures outputs chain correctly and each discipline receives appropriately scoped work.

Orchestrators bypass decomposition due to missing anti-temptation rules. The Skill enforces guardrails that require creating tasks via kanban_create with a clear task graph, preventing the orchestrator role from self-executing concrete tasks.