kanban-orchestrator

Decompose complex goals into Kanban tasks routed to Hermes profiles.

Updated Apr 9, 2026

Search Tags:#automation #dependency management #orchestration #task decomposition #kanban #Hermes #multi-agent routing

Ready to run

npx skills add https://github.com/MarbleSodas/Mavis --skill kanban-orchestrator-marblesodas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kanban-orchestrator
Source: https://github.com/MarbleSodas/Mavis/tree/main/skills/devops/kanban-orchestrator
Command: npx skills add https://github.com/MarbleSodas/Mavis --skill kanban-orchestrator-marblesodas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates multi-step, multi-specialist work by decomposing user goals into Kanban tasks while preventing the system from “just doing the work itself.”

Core Features & Use Cases

Profile discovery before planning: Finds which Hermes profiles exist locally so routing does not silently fail on unknown assignees.
Decomposition into a task graph: Extracts lanes, maps each lane to the right profile, and links tasks with correct parent dependencies.
Anti-temptation guardrails: Enforces “decompose, don't execute” by always creating assigned Kanban tasks for concrete work.

Quick Start

Tell your Hermes user request to be decomposed and routed (for example: “Plan and execute a multi-lane Kanban workflow to research, synthesize, and draft a decision memo”), then follow the orchestrator’s task graph approval before it creates tasks.

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 complex goal into parallel workstreams without the agent executing the tasks directly?▼

Kanban task decomposition routes a complex goal into a parallel workstream graph, assigning each lane to the appropriate Hermes profile via Kanban cards instead of executing the work directly. It enforces an orchestration-only guardrail to prevent premature execution.

What is multi-agent routing for fan-out and fan-in research workflows?▼

Multi-agent routing maps decomposed workstreams to specific Hermes profiles, enabling fan-out research workflows and gated synthesis steps. It links tasks with correct parent dependencies and uses crash-safe persistence via Kanban rows to track the entire workflow.

How do I set up Kanban orchestration to route tasks to different specialist profiles?▼

To set up Kanban orchestration, first discover available Hermes profiles locally to prevent routing failures. Then define the user goal, approve the generated task graph, and use kanban_create to generate assigned cards with correct parent dependencies for each specialist.

Do I need to manually discover Hermes profiles before creating a Kanban workflow?▼

Profile discovery happens automatically before planning to ensure routing does not silently fail on unknown assignees. The orchestrator checks which Hermes profiles exist locally, maps workstreams to them, and then creates the dependent Kanban tasks.

Why does my multi-agent orchestrator execute work instead of delegating it to specialist lanes?▼

An orchestrator executes work directly when anti-temptation guardrails are missing. This Skill enforces a decompose-don't-execute rule by ensuring every concrete action becomes an assigned Kanban card routed to a specialist, preventing the system from doing the work itself.

Can I use Kanban orchestration for gated synthesis and review steps in a multi-lane workflow?▼

Yes, Kanban orchestration applies to scenarios with parallel lanes, fan-out/fan-in research workflows, and gated synthesis or review steps. It creates tasks with correct parent dependencies to ensure review gates are respected before downstream synthesis begins.