kanban-orchestrator

Decompose tasks and route them across Kanban-enabled multi-agent work streams.

Updated May 21, 2026
One-click install
npx skills add https://github.com/samlaggz/hermes-agent-sam --skill kanban-orchestrator-samlaggz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kanban-orchestrator
Source: https://github.com/samlaggz/hermes-agent-sam/tree/main/backup/skills/devops/kanban-orchestrator
Command: npx skills add https://github.com/samlaggz/hermes-agent-sam --skill kanban-orchestrator-samlaggz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured decomposition and routing framework for Kanban-based multi-agent workflows, ensuring the orchestrator directs work without executing it.

Core Features & Use Cases

  • Decomposition governance: derives task cards from goals, constraints, and available profiles.
  • Route-first execution model: assigns tasks to appropriate profiles while keeping the initiator out of execution.
  • Dependency-aware orchestration: supports parallel lanes and gated tasks with clear handoffs and audit trails.
  • Real-world scenario: multiple teams coordinate on a product rollout by decomposing milestones into independent cards and synthesizing final decisions.

Quick Start

Tell Hermes to initialize an orchestrator task flow for your current profiles and workflow.

Frequently Asked Questions about kanban-orchestrator

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

FAQPage Schema
How do I route tasks across multi-agent workflows without the orchestrator executing them?

Kanban orchestration routes tasks across multi-agent workflows by decomposing goals into Kanban cards and assigning them to profiles. The orchestrator directs work and enforces anti-temptation rules without executing tasks, producing an auditable task graph.

What is the best way to manage dependencies and parallelization in multi-agent task routing?

Multi-agent task routing handles dependencies by supporting parallel lanes and gated tasks. The orchestrator coordinates profiles and workers with clear handoffs, ensuring dependency-aware execution and a complete audit trail across work streams.

How does task decomposition work for Kanban-based multi-agent orchestration?

Task decomposition derives Kanban cards from goals, constraints, and available profiles. It governs the breakdown process to ensure the orchestrator assigns tasks appropriately while keeping the initiator out of execution.

Can I coordinate multiple teams on a product rollout using Kanban orchestration?

Kanban orchestration coordinates multiple teams on a product rollout by decomposing milestones into independent cards. Teams work in parallel lanes with gated tasks, and the orchestrator synthesizes final decisions from the auditable task graph.

Do I need specific worker profiles configured before initializing Kanban orchestration?

Kanban orchestration requires available profiles to route tasks effectively. The decomposition governance derives task cards based on your current profiles and workflow, meaning you must define worker profiles before initializing the orchestrator task flow.

When should I not use a route-first execution model for multi-agent workflows?

A route-first execution model is not suitable when tasks require the orchestrator to directly execute work rather than delegate. Kanban orchestration enforces anti-temptation rules to keep the initiator out of execution, making it unfit for hands-on processing.