kanban-orchestrator

Decomposes goals into Kanban task graphs and routes cards to worker profiles.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/CHENHUI-X/toolbox --skill kanban-orchestrator-chenhui-x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kanban-orchestrator
Source: https://github.com/CHENHUI-X/toolbox/tree/main/custom-skills/devops/kanban-orchestrator
Command: npx skills add https://github.com/CHENHUI-X/toolbox --skill kanban-orchestrator-chenhui-x

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When acting as an orchestrator in a multi-agent Kanban setup, it is easy to do the work yourself, invent profile names that silently fail, or mislink task dependencies. This Skill provides a decomposition playbook and anti-temptation rules so work is routed to the right specialist profiles instead of executed directly. ## Core Features & Use Cases - Profile discovery first: Run hermes profile list or ask the user before fanning out, since the dispatcher silently drops unknown assignees. - Task graph decomposition: Extract independent lanes, create parallel cards, and gate dependent cards with parents=[...] so children stay in todo until parents finish. - Stuck worker recovery: Reclaim, reassign, or change a profile's model when a worker crashes or hallucinates card completions. - Use Case: A user asks to "research Postgres migration and draft a memo." You create 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 decompose my goal into Kanban tasks and assign each one to the appropriate existing profile.

Frequently Asked Questions about kanban-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decompose a request into Kanban tasks for multiple agents?

Extract independent workstreams as separate cards with no parent links so they run in parallel, then create synthesis or review cards with parents=[...] referencing the lane task ids. Children stay in todo until every parent reaches done.

When should I use the Kanban board instead of doing the task directly?

Use the board when multiple specialists are needed, work must survive restarts, tasks 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.

Why does my Kanban card sit in ready forever without being picked up?

The dispatcher silently fails to spawn unknown assignee names, so the card was likely assigned to a profile that does not exist. Run hermes profile list to discover configured profiles and reassign the card to a real one.

How do I make one Kanban task wait for another to finish?

Pass parents=[parent_task_id] in the child's kanban_create call. The child starts in todo and the dispatcher auto-promotes it to ready only after every parent completes; do not create it first and link later.

How do I recover a stuck or crashing Kanban worker?

Use hermes kanban reclaim <task_id> to abort the worker and reset the task to ready, or reassign it to a different profile with --reclaim. If the model is the problem, edit the profile config and reclaim to retry.