team-agent-orchestration

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. Operating Model Treat every agent as a teammate with a narrow contract: Show more Installs 1.1K Repository affaan-m/ecc GitHub Stars 239.2K First Seen Jun 4, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass