kanban-orchestrator

Decomposes goals into Kanban task graphs and routes work to agent profiles.

Updated May 18, 2026
One-click install
npx skills add https://github.com/ossoolli/Nexum-Core --skill kanban-orchestrator-ossoolli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kanban-orchestrator
Source: https://github.com/ossoolli/Nexum-Core/tree/main/skills/devops/kanban-orchestrator
Command: npx skills add https://github.com/ossoolli/Nexum-Core --skill kanban-orchestrator-ossoolli

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 the decomposition playbook and anti-temptation rules for routing work through the board instead of executing it. ## Core Features & Use Cases - Profile Discovery First: Grounds every plan in the profiles that actually exist on the machine via hermes profile list, preventing cards from sitting in ready forever due to unknown assignees. - Task Graph Decomposition: Extracts independent lanes from a request, maps them to profiles, and creates parallel cards plus parent-gated synthesis cards using kanban_create with parents=[...]. - Worker Recovery: Covers reclaiming stuck tasks, reassigning to a different profile, and changing a profile's model when workers crash or hallucinate. - Use Case: A user asks to "research Postgres migration costs and performance, then draft a CTO memo." The orchestrator fans out two parallel research cards, gates a synthesis card on both, and gates the memo draft on the synthesis. ## Quick Start Act as the kanban orchestrator: list my available profiles, then decompose my request into linked Kanban tasks and assign each to the right 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 the independent lanes from the request, map each lane to an existing 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.

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, 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.

Why is my Kanban card stuck in ready and never picked up?▼

The dispatcher silently fails to spawn unknown assignee names, so a card assigned to a nonexistent profile sits in ready forever. Run hermes profile list to discover configured profiles and assign only to names that exist.

How do I recover a stuck or crashing Kanban worker?▼

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

Should I create all Kanban cards in parallel and link dependencies afterward?▼

No. Create parent cards first, capture their returned ids, and pass them in the child card's parents list during kanban_create. Linking afterward creates a window where the dispatcher can claim a child before its inputs exist.