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:
- 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.
Agent Kanban
Use agent Kanban when work must be visible across sessions.
| Column |
Meaning |
Exit Criteria |
| Backlog |
Candidate work item, not yet shaped |
Acceptance criteria written |
| Ready |
Shaped and assignable |
Owner and branch/worktree assigned |
| Running |
Agent is actively working |
Handoff artifact and changed files exist |
| Review |
Work is complete but not merged |
Tests, diff review, and risk check pass |
| Blocked |
Needs external input or failed gate |
Blocker has owner and next action |
| Merged |
Integrated into mainline |
PR merged or local main updated |
| Archived |
No longer relevant |
Reason recorded |
Each card should fit this schema:
{
"id": "agent-card-001",
"title": "Build dynamic workflow skill",
"owner": "codex",
"state": "running",
"branch": "product/dynamic-workflow-team-orchestration",
"worktree": ".",
"acceptance": [
"Skill exists",
"Tests cover required concepts",
"Content artifact contains video and article angles"
],
"merge_gate": "lint, focused tests, and catalog check pass",
"handoff": "path/to/handoff.md"
}
Team-Based Orchestration Flow
- Shape the board: convert fuzzy ambition into work items with owners and merge gates.
- Pick execution mode: single-agent, dynamic workflow mode, dmux/tmux, worktree fan-out, or external desktop orchestrator.
- Assign boundaries: one owner per card, clear file scope, and no overlapping writes without an integrator.
- Run agents: each agent writes evidence and handoff notes, not just code.
- Review in sequence: tests first, then diff review, then security/risk checks, then content/product polish.
- Merge deliberately: one integrator resolves conflicts and updates the control pane or status artifact.
- Extract reusable skill: if the card pattern repeats, promote it into
skills/.
Control Pane Requirements
A useful control pane for team orchestration should show:
- Active work items and their agent Kanban state.
- Owner, harness, branch, worktree, and last heartbeat.
- Links to handoff artifacts, tests, screenshots, and PRs.
- Blockers grouped by owner and unblock action.
- Merge readiness by gate, not vibes.
- Reusable workflow candidates that should become shared skills.
Do not add more automation until the operator can answer: who owns this, what changed, what gate failed, and what can safely merge?
Dynamic Workflow Compatibility
When a card needs dynamic workflow mode:
- Put the task-local harness under the card owner.
- Store inputs and outputs on the card.
- Require an eval before moving from Running to Review.
- Promote the harness to a shared skill only after repeat use.
Failure Modes To Watch
- Agent soup: many agents running, no owner or merge gate.
- Invisible work: useful output exists only in a chat transcript.
- Board theater: a Kanban board exists but cards have no acceptance criteria.
- Overlapping writes: parallel agents edit the same files without worktrees.
- No product artifact: the process produces docs but no runnable or publishable surface.
Output Standard
Finish each orchestration pass with:
- Board/card changes.
- Merged or pending branches.
- Tests and eval evidence.
- Blockers with owner and next action.
- New shared skill candidates.
1---2name: team-agent-orchestration3description: "Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates. Use when coordinating multiple agents in parallel across branches or worktrees — multi-agent fan-out, agent Kanban, squad coordination, or merging agent output into one product."4metadata:5 source: https://skillmd.com/skills/junmystery/team-agent-orchestration6 origin: ECC7---89# Team Agent Orchestration1011Use 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.1213## When To Activate1415- The task spans multiple agents, tools, harnesses, branches, or worktrees.16- 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.17- A project needs shared workflow state across people and agents.18- Existing agent fan-out is producing output but not mergeable product.1920## Operating Model2122Treat every agent as a teammate with a narrow contract:2324- **Owner**: the person or agent accountable for the work item.25- **Scope**: files, branch, tool surface, and forbidden areas.26- **State**: backlog, ready, running, review, blocked, merged, or archived.27- **Evidence**: tests, screenshots, logs, review notes, or eval reports.28- **Merge gate**: the exact condition that allows integration.2930## Agent Kanban3132Use agent Kanban when work must be visible across sessions.3334| Column | Meaning | Exit Criteria |35| --- | --- | --- |36| Backlog | Candidate work item, not yet shaped | Acceptance criteria written |37| Ready | Shaped and assignable | Owner and branch/worktree assigned |38| Running | Agent is actively working | Handoff artifact and changed files exist |39| Review | Work is complete but not merged | Tests, diff review, and risk check pass |40| Blocked | Needs external input or failed gate | Blocker has owner and next action |41| Merged | Integrated into mainline | PR merged or local main updated |42| Archived | No longer relevant | Reason recorded |4344Each card should fit this schema:4546```json47{48 "id": "agent-card-001",49 "title": "Build dynamic workflow skill",50 "owner": "codex",51 "state": "running",52 "branch": "product/dynamic-workflow-team-orchestration",53 "worktree": ".",54 "acceptance": [55 "Skill exists",56 "Tests cover required concepts",57 "Content artifact contains video and article angles"58 ],59 "merge_gate": "lint, focused tests, and catalog check pass",60 "handoff": "path/to/handoff.md"61}62```6364## Team-Based Orchestration Flow65661. **Shape the board**: convert fuzzy ambition into work items with owners and merge gates.672. **Pick execution mode**: single-agent, dynamic workflow mode, dmux/tmux, worktree fan-out, or external desktop orchestrator.683. **Assign boundaries**: one owner per card, clear file scope, and no overlapping writes without an integrator.694. **Run agents**: each agent writes evidence and handoff notes, not just code.705. **Review in sequence**: tests first, then diff review, then security/risk checks, then content/product polish.716. **Merge deliberately**: one integrator resolves conflicts and updates the control pane or status artifact.727. **Extract reusable skill**: if the card pattern repeats, promote it into `skills/`.7374## Control Pane Requirements7576A useful control pane for team orchestration should show:7778- Active work items and their agent Kanban state.79- Owner, harness, branch, worktree, and last heartbeat.80- Links to handoff artifacts, tests, screenshots, and PRs.81- Blockers grouped by owner and unblock action.82- Merge readiness by gate, not vibes.83- Reusable workflow candidates that should become shared skills.8485Do not add more automation until the operator can answer: who owns this, what changed, what gate failed, and what can safely merge?8687## Dynamic Workflow Compatibility8889When a card needs dynamic workflow mode:9091- Put the task-local harness under the card owner.92- Store inputs and outputs on the card.93- Require an eval before moving from Running to Review.94- Promote the harness to a shared skill only after repeat use.9596## Failure Modes To Watch9798- **Agent soup**: many agents running, no owner or merge gate.99- **Invisible work**: useful output exists only in a chat transcript.100- **Board theater**: a Kanban board exists but cards have no acceptance criteria.101- **Overlapping writes**: parallel agents edit the same files without worktrees.102- **No product artifact**: the process produces docs but no runnable or publishable surface.103104## Output Standard105106Finish each orchestration pass with:107108- Board/card changes.109- Merged or pending branches.110- Tests and eval evidence.111- Blockers with owner and next action.112- New shared skill candidates.