team-agent-orchestration

Topics in the source

• Team Agent Orchestration
• When To Activate
• Operating Model
• Agent Kanban
• Team-Based Orchestration Flow
• Control Pane Requirements
• Dynamic Workflow Compatibility
• Failure Modes To Watch

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. 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. Treat every agent as a teammate with a narrow contract: Owner: the person or agent accountable for the work item. Scope: files, branch, tool surface, and forbidden areas. State: backlog, ready, running, review, blocked, merged, or archived. Evidence: tests, screenshots, logs, review notes, or eval reports. Merge gate: the exact condition that allows integration. Use agent Kanban when work must be visible across sessions. | Column | Meaning | Exit Criteria | | --- | --- | --- | | Backlog | Candidate work item, not yet shaped | Acceptance criteria

This is an excerpt. Refer to the complete source and its current requirements.