kanban-orchestrator

Extract independent work lanes from the request, map each lane to an existing worker profile, and create one card per lane with kanban_create. Gate dependent cards by passing parent task ids in the parents list so children stay in todo until all parents finish.

First discover which profiles exist using hermes profile list or by asking the user, then assign cards only to those names. The dispatcher silently fails to spawn unknown assignees, so an invented profile name leaves the card stuck in ready forever.

Use the board when multiple specialists are needed, work must survive restarts, subtasks can run in parallel, review loops are expected, or an audit trail matters. For small one-shot reasoning tasks, use delegate_task or answer directly instead.

goal_mode=True wraps the worker in a judge-evaluated loop that re-checks the card against its title and body after each turn, keeping the same session until completion or budget exhaustion. Use it for long multi-step cards with explicit acceptance criteria, not cheap one-shot tasks.

Use the dashboard Recovery section or CLI: reclaim aborts the worker and resets the task to ready, reassign switches it to a different existing profile, and changing the profile's model on disk plus a reclaim retries with the new model.

This happens when cards are created as independent ready cards instead of being linked. Pass parent ids in the parents list during the child's kanban_create call so the dependency engine keeps it in todo until every parent reaches done.