team-agent-orchestration

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Team Agent Orchestration

团队Agent编排

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.

当Agent被作为团队而非单个助手进行管理时，可使用此Skill。其目的是让基于团队的编排更可靠：清晰的工作项、明确的所有权、Agent看板状态、分支隔离、控制面板可见性以及合并门控。

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.

任务涉及多个Agent、工具、harness、分支或工作树。
用户提及团队编排、Agent看板、squad、指挥器、控制面板、管理器、桌面应用、Zellij、tmux、Hermes、Devin、Codex、Claude Code或多Agent工作。
项目需要跨人员和Agent共享工作流状态。
现有的Agent分支输出了内容，但无法合并为可交付产品。

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视为具有明确契约的团队成员：

负责人：对工作项负责的人员或Agent。
范围：文件、分支、工具范围以及禁止操作区域。
状态：待办、就绪、运行中、审核中、阻塞、已合并或已归档。
证据：测试、截图、日志、审核笔记或评估报告。
合并门控：允许集成的具体条件。

Agent Kanban

Agent看板

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:

json

{
  "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"
}

当工作需要跨会话可见时，使用Agent看板。

列名	含义	退出标准
待办（Backlog）	候选工作项，尚未明确需求	编写完成验收标准
就绪（Ready）	需求明确且可分配	已分配负责人和分支/工作树
运行中（Running）	Agent正在积极工作	存在交接工件和已修改文件
审核中（Review）	工作已完成但未合并	测试、差异审核和风险检查通过
阻塞（Blocked）	需要外部输入或未通过门控	阻塞问题已指定负责人和下一步行动
已合并（Merged）	已集成到主线	PR已合并或本地主线已更新
已归档（Archived）	不再相关	已记录原因

每个卡片应符合以下schema：

json

{
  "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/
```
.

规划看板：将模糊的目标转化为带有负责人和合并门控的工作项。
选择执行模式：单Agent、动态工作流模式、dmux/tmux、工作树分支或外部桌面编排器。
分配边界：每个卡片对应一个负责人，明确文件范围，无集成者时禁止重叠写入。
运行Agent：每个Agent不仅编写代码，还要生成证据和交接笔记。
按顺序审核：先进行测试，再进行差异审核，接着是安全/风险检查，最后是内容/产品打磨。
谨慎合并：由一名集成者解决冲突并更新控制面板或状态工件。
提取可复用Skill：如果卡片模式重复出现，将其升级到
```
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?

一个实用的团队编排控制面板应显示：

活跃工作项及其Agent看板状态。
负责人、harness、分支、工作树和最后心跳时间。
指向交接工件、测试、截图和PR的链接。
按负责人分组的阻塞问题及解决行动。
基于门控的合并就绪状态，而非主观判断。
应转化为共享Skill的可复用工作流候选。

在操作者能够回答以下问题之前，不要添加更多自动化：谁负责这项工作、发生了哪些变更、哪个门控未通过、哪些内容可以安全合并？

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.

当卡片需要动态工作流模式时：

将任务本地的handoff归为卡片负责人所有。
将输入和输出存储在卡片上。
从“运行中”状态转到“审核中”状态前，必须完成评估。
仅在重复使用后，才将harness升级为共享Skill。

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.

Agent混乱：多个Agent在运行，但没有负责人或合并门控。
不可见工作：有用的输出仅存在于聊天记录中。
看板形式化：存在Kanban看板，但卡片没有验收标准。
重叠写入：并行Agent在无工作树的情况下编辑同一文件。
无产品工件：流程仅生成文档，没有可运行或可发布的成果。

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.

每次编排完成后，需交付：

看板/卡片的变更。
已合并或待处理的分支。
测试和评估证据。
带有负责人和下一步行动的阻塞问题。
新的共享Skill候选。