Verified:GitHub

kanban-orchestrator

Decompose complex goals into Kanban tasks with dependency gating and specialist routing.

Updated May 4, 2026

Search Tags:#task decomposition #kanban #multi-agent orchestration #workflow planning #specialist routing #dependency gating

Ready to run

npx skills add https://github.com/JamesFincher/gengar --skill kanban-orchestrator-jamesfincher

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill prevents an orchestrator from skipping decomposition by enforcing a Kanban-based workflow that routes work to the right specialist, while preserving an audit trail of tasks.

Core Features & Use Cases

Orchestrator role playbook: Provides conventions for researcher/analyst/writer/reviewer and engineering/ops/pm specialties so routing stays consistent.
Kanban decomposition lifecycle: Instructs how to understand goals, sketch a task graph, create linked tasks with dependency gates, and report back after completion.
Anti-temptation safeguards: Enforces "decompose, route, and summarize" so the orchestrator does not execute the work directly, including reassignment guidance for reviewer-needed changes.

Quick Start

Use the kanban-orchestrator skill when you need to plan and route multi-step work (e.g., research, synthesize, write, review) to multiple specialists using a persistent Kanban board.

Frequently Asked Questions about kanban-orchestrator

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

FAQPage Schema

How do I route multi-step work to different specialists without losing track of dependencies?▼

Multi-agent orchestration routes work by decomposing goals into a Kanban task graph with parent-child dependencies and gating, ensuring specialist routing stays consistent and preserves an audit trail.

What is the best way to decompose ambiguous goals into structured tasks for an orchestrator?▼

Task decomposition breaks ambiguous goals into a Kanban lifecycle: understand objectives, sketch a task graph, create linked tasks with dependency gates, and summarize results for human-in-the-loop review.

How do I prevent my orchestrator from executing work directly instead of routing it?▼

Anti-temptation safeguards enforce a strict decompose, route, and summarize playbook, preventing the orchestrator from executing work directly and providing reassignment guidance for reviewer-needed changes.

Can I maintain a consistent specialist roster for workflow planning across restarts?▼

Yes, workflow planning uses consistent specialist-roster conventions for research, analysis, writing, reviewing, engineering, ops, and PM roles, ensuring routing survives restarts and supports iterative interventions.

Does multi-agent orchestration work for iterative workflows that require human-in-the-loop interventions?▼

Yes, multi-agent orchestration applies to iterative workflows by maintaining a persistent Kanban board with dependency gating, which supports human-in-the-loop interventions and preserves task state across restarts.