kanban-orchestrator

Decompose user goals into a Kanban task graph with dependency-linked cards.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/devMoez/titan --skill kanban-orchestrator-devmoez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kanban-orchestrator
Source: https://github.com/devMoez/titan/tree/main/skills/devops/kanban-orchestrator
Command: npx skills add https://github.com/devMoez/titan --skill kanban-orchestrator-devmoez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill helps you decompose a complex goal into Kanban tasks and route each lane to the right specialist profile instead of executing everything yourself.

Core Features & Use Cases

  • Orchestrator playbook: Turns an ambiguous or multi-lane request into a task graph with explicit fan-out and fan-in.
  • Anti-temptation guardrails: Enforces “decompose, don't execute” and requires creating a Kanban task for every concrete work item.
  • Dependency-safe linking: Uses parent gating so synthesis/review tasks only run after prerequisite cards finish.
  • Profile discovery first: Prevents silent dispatcher failures by grounding routing in the profiles actually configured on your machine.

Use Case: You ask the agent to “fix blockers and produce a migration decision memo,” and it creates parallel research/verification and implementation tasks, then synthesizes findings into a single memo with correct dependencies.

Quick Start

Run the kanban-orchestrator guidance by first discovering available profiles, sketching a task graph to match your request, then creating one Kanban card per lane and linking synthesis cards with parent dependencies.

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 engineering goal into a multi-agent task graph?

To decompose a complex engineering goal into a multi-agent task graph, you sketch parallel independent lanes for each work item, create a Kanban card per lane, and link synthesis cards using parent dependencies for correct gating.

What is the best way to route work to specialist profiles without executing tasks directly?

Routing work to specialist profiles without direct execution requires discovering available profiles first, then using an orchestrated Kanban playbook to dispatch each task card to the configured assignee.

How does dependency gating work for synthesis and review tasks in workflow automation?

Dependency gating for synthesis tasks in workflow automation uses parent links to prevent downstream review or synthesis cards from running until all prerequisite parallel work cards finish successfully.

Can I use kanban orchestration for parallel research and implementation workstreams?

Yes, you can use kanban orchestration for parallel research and implementation workstreams by creating independent cards for each lane and synthesizing the findings into a final report.

Why do I need to discover configured profiles before routing multi-agent tasks?

You need to discover configured profiles before routing multi-agent tasks to prevent silent dispatcher failures and ensure every Kanban card is assigned to a valid specialist actually available on your machine.

What are the limitations of using a Kanban orchestrator for task decomposition?

The main limitation of using a Kanban orchestrator for task decomposition is its strict anti-temptation guardrail: it enforces a decompose-only rule, preventing the agent from executing any concrete work item directly.