What problem does it solve? Multi-agent setups fail when an orchestrator does the work itself, invents nonexistent profile names, or creates dependent tasks as independent cards. This Skill provides the decomposition playbook and anti-temptation rules for routing work through a Kanban board instead of executing it directly. ## Core Features & Use Cases - Profile Discovery First: Requires listing actual configured profiles (via hermes profile list or asking the user) before fan-out, since the dispatcher silently drops unknown assignees. - Task Graph Decomposition: Splits multi-lane requests into parallel independent cards and gated child cards using parents=[...] in kanban_create, with patterns like fan-out/fan-in, pipeline gates, and same-profile queues. - Stuck Worker Recovery: Covers reclaim, reassign, and model-change workflows for crashing or hallucinating workers, including hallucination audit events. - Use Case: A user asks to "research Postgres migration and draft a memo." The orchestrator creates two parallel research cards, a synthesis card gated on both, and a memo-drafting card gated on the synthesis, each assigned to real profiles on the machine. ## Quick Start Ask the orchestrator to break down a multi-step goal into Kanban cards assigned to your available worker profiles and report the resulting task graph.
