What problem does it solve? When acting as an orchestrator agent, it is tempting to execute work directly instead of routing it, and multi-agent work without structure loses audit trails, crash recovery, and parallelism. This playbook enforces disciplined decomposition of goals into dependency-linked Kanban tasks assigned to specialist profiles. ## Core Features & Use Cases - Decomposition Playbook: A five-step workflow covering goal clarification, task-graph sketching, task creation with kanban_create, parent-linking for gated promotion, and reporting back to the user. - Specialist Roster Conventions: Standard profile table (researcher, analyst, writer, reviewer, backend-eng, frontend-eng, ops, pm) with typical workspace assignments. - Anti-Temptation Rules: Explicit constraints preventing the orchestrator from executing work itself, with escalation to the user when no specialist fits. - Use Case: For a request like "analyze whether we should migrate to Postgres," create two parallel researcher tasks, an analyst task parented on both, and a writer task parented on the analyst, letting the dispatcher handle scheduling automatically. ## Quick Start Ask the orchestrator to break down your project into Kanban tasks and assign each one to the right specialist profile.
