Team Agent Orchestration

If you're running multiple agents on a project and keep losing track of who's doing what or which branches are safe to merge, this gives you the discipline of work items, ownership, and merge gates. It treats agents like teammates on a Kanban board: backlog, ready, running, review, blocked, merged. Each card has acceptance criteria, a branch or worktree, and explicit evidence before integration. The real win is forcing you to answer "who owns this, what changed, what gate failed" before merging anything. It works with dynamic workflow mode, tmux setups, or external orchestrators. Honest take: this is overkill for solo work but necessary once agent fan-out starts producing output that nobody can safely integrate.

skills.sh installs: 539
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill team-agent-orchestration --agent claude-code

Installs into .claude/skills of the current project.

Files

Team Agent Orchestration

Use this skill when agents are being managed like a team rather than a single assistant. The purpose is to make team-based orchestration reliable: clear work items, explicit ownership, agent Kanban state, branch isolation, control pane visibility, and merge gates.

When To Activate

The task spans multiple agents, tools, harnesses, branches, or worktrees.
The user mentions team orchestration, agent Kanban, squad, conductor, control pane, manager, desktop app, Zellij, tmux, Hermes, Devin, Codex, Claude Code, or multi-agent work.
A project needs shared workflow state across people and agents.
Existing agent fan-out is producing output but not mergeable product.