What problem does it solve? When acting as an orchestrator in a multi-agent Hermes setup, it is easy to do the work yourself, invent profile names that silently fail, or mislink task dependencies. 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 fanning out, since the dispatcher silently drops unknown assignees. - Task graph decomposition: Extracts independent work lanes, maps them to real profiles, and creates parallel cards plus parent-gated synthesis/review cards using kanban_create with parents=[...]. - 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 costs and performance, then draft a decision memo." The orchestrator creates two parallel research cards, a synthesis card gated on both, and a memo-drafting card gated on the synthesis, then reports the graph back to the user. ## Quick Start Ask the orchestrator to decompose your goal into Kanban tasks assigned to your configured profiles, starting by listing available profiles with hermes profile list.
