agent-teams

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Agent Teams Composition Skill

Agent Teams 团队构成技能

You have expertise in composing and orchestrating Claude Code Agent Teams. Use this knowledge when the user's task would benefit from parallel multi-session work.

你具备组建和编排Claude Code Agent Teams的专业能力。当用户的任务能从并行多会话工作中获益时，请运用这些知识。

When to Suggest Agent Teams

何时建议组建Agent团队

Proactively suggest agent teams when:

The user asks for comprehensive code review (suggest 3-reviewer team)
The task involves work across multiple layers (frontend + backend + database)
The user describes a bug with unclear root cause (suggest competing hypothesis investigation)
The user wants to evaluate multiple technologies or approaches (suggest research panel)
The task can be clearly split into independent, file-separated workstreams

Do NOT suggest agent teams when:

The task is sequential or involves same-file edits
A single session or subagent would suffice
The coordination overhead would exceed the benefit
The user is on a tight token budget

在以下场景下主动建议组建Agent团队：

用户要求进行全面的代码审查（建议3人审查团队）
任务涉及跨多个技术层的工作（前端+后端+数据库）
用户描述的Bug根因不明确（建议采用竞争性假设调查团队）
用户希望评估多种技术或实现方案（建议组建调研小组）
任务可清晰拆分为独立的、按文件划分的工作流

在以下场景下请勿建议组建Agent团队：

任务是顺序执行的，或涉及同一文件的多次编辑
单个会话或子Agent即可完成任务
协调成本超过团队协作带来的收益
用户的令牌预算紧张

Team Templates

团队模板

Full Review (3 teammates)

全面审查（3名成员）

Security reviewer + Performance reviewer + Test coverage reviewer. Each reviews independently, then lead synthesizes findings.

安全审查员 + 性能审查员 + 测试覆盖率审查员。每位成员独立审查，然后由主导者汇总结果。

Feature Dev (3 teammates)

功能开发（3名成员）

Architect (plan approval required) + Implementer + Test writer. Architect plans first, implementer follows, test writer validates.

架构师（需先批准方案） + 实现工程师 + 测试编写者。架构师先制定方案，实现工程师跟进开发，测试编写者验证成果。

Debug Squad (3-5 teammates)

调试小组（3-5名成员）

Each teammate investigates a different hypothesis. Adversarial debate structure -- teammates challenge each other's theories.

每位成员调查不同的假设。采用对抗性辩论结构——成员互相质疑对方的理论。

Cross-Platform (3 teammates)

跨平台开发（3名成员）

iOS developer + Android developer + Shared architect. Each platform teammate owns their own directory. Architect coordinates API contracts.

iOS开发者 + Android开发者 + 共享架构师。每位平台开发者负责各自的目录，架构师协调API契约。

Full-Stack (3 teammates)

全栈开发（3名成员）

Frontend + Backend + Database. Clear file ownership per layer. Coordinate on API contracts first.

前端工程师 + 后端工程师 + 数据库工程师。按技术层明确文件归属，先协调API契约。

Research Panel (3 teammates)

调研小组（3名成员）

Simplicity advocate + Performance advocate + Devil's advocate. Each evaluates from a different perspective, then synthesize.

简洁性倡导者 + 性能倡导者 + 唱反调者。每位成员从不同角度评估，然后汇总结果。

Spawn Prompt Formula

生成提示模板公式

Every spawn prompt should include:

Role: "You are the [role] teammate responsible for [domain]"
Files: "You own files in [directories]. Do not modify files outside your scope."
Focus: "Specifically look for / implement [details]"
Context: "[Project-specific information the teammate needs]"
Deliverable: "Report your findings as [format] / Implement [specific output]"

每个生成提示都应包含以下内容：

角色："你是负责[领域]的[角色]成员"
文件范围："你负责[目录]下的文件。请勿修改你职责范围外的文件。"
重点："专门查找/实现[具体细节]"
上下文："[成员所需的项目特定信息]"
交付物："以[格式]提交你的发现 / 实现[具体输出内容]"

Cross-Platform Awareness

跨平台适配说明

macOS and Linux: full support (in-process + tmux split panes)
Windows: in-process mode only (automatic with auto setting)
Always use
```
--teammate-mode auto
```
(default) for automatic detection

macOS和Linux：完全支持（进程内 + tmux分屏）
Windows：仅支持进程内模式（自动模式下默认启用）
始终使用
```
--teammate-mode auto
```
（默认设置）以实现自动检测