What does this skill do?

Skill Agent Team Orchestration transforms vague objectives into work items with designated owners, acceptance criteria, and explicit integration points. It coordinates teams of agents using Kanban boards, isolates branches with worktrees, and employs a single integrator that resolves conflicts, ensuring that the fan-out of agents produces mergeable outputs rather than just scattered results.

Agent Kanban Board
Turn vague objectives into task cards with clearly defined owners, departments, acceptance criteria, and integration points.
Multi-Agent Execution with Worktrees
Run agents in parallel using thread and worktree isolation to prevent overlapping writes to the same files.
Sequential Review and Merging
Check tests first, then diffs, then security/risk, and finally polish, with a single integrator who merges deliberately.
Extraction of Reusable Skills
Identify recurring patterns in the cards and promote them to shared skills for future orchestrations.

Usage examples

📋 Set up dashboard
Create a Kanban board with 5 cards to build a dynamic flow skill, assigning responsible parties and acceptance criteria to each one.
🔀 Run agents in parallel
Launch 3 agents in separate worktrees to implement the backend, frontend, and tests for my project, without the files overlapping.
🔍 Review before merging
Review the agent branches: first the tests, then the diff, next the security risk, and finally merge whatever passes all the checks.
♻️ Promote a pattern
Identify which cards on the board follow the same workflow pattern and promote that workflow to a reusable skill.

Features

Kanban Boards with Statuses Backlog columns moved to "Archived" based on defined exit criteria: assigned owner, branch created, tests passed, and PR merged.
Isolation of branches and worktrees Each agent works in its own branch and worktree to avoid overlapping writes and unmanaged conflicts.
Explicit integration gates Each pull request defines its own `merge_gate`: lint, targeted tests, and checks that must be passed before merging.
Evidence and Transfer Each agent generates verifiable evidence (tests, logs, screenshots) and handover notes—not just standalone code.
Traceable Control Panel Answer at any time: Who is responsible, what changed, which gateway failed, and what can be safely merged.

Frequently asked questions

Yes, isolating branches and worktrees requires Git to be configured in your repository. If you're only using an agent, you can skip the worktrees.
There is no set limit, but the skill recommends one person in charge per card and a single mediator to resolve conflicts. The more agents there are, the more critical the board becomes.
Single agent, dynamic flow, dmux/tmux, fan-out by worktree or an external desktop orchestrator. Choose based on the complexity of the task.
The skill detects the failure mode of overlapping writes and requires separate worktrees or an integrator that sequences the writes before merging.
Agent Team Orchestration — Multi-agent coordination with Claude AI

¿Prefieres escuchar el contenido? Genera la narración de audio con un clic.