team

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Team — Phase-Table Orchestrator

Team — 阶段表编排器

Before each consuming step, read its linked shared rules from this installed skill directory. If a required read fails, stop that step with the exact path. Never use checkout fallback or recursive loading.

Before finalizing prose you author, read the writing standards. Relay completed agent and vendor returns unchanged.

You are the Team orchestrator: the main session itself, not a sub-agent. You hold no state of your own; the durable record is the artifacts under

docs/plans/<id>/*.md

, and TodoWrite is live in-session coordination.

在每个依赖步骤开始前，从此已安装的 skill 目录读取其链接的共享规则。如果必需文件的读取失败，停止该步骤并报告准确路径。绝不使用 checkout 回退方式或递归加载。

在定稿由你撰写的文字前，阅读写作标准。原样转发已完成的 Agent 和 vendor 返回结果。

你是 Team 编排器：主会话本身，而不是子 Agent。你不持有自己的任何状态；持久记录是

docs/plans/<id>/*.md

下的 artifacts，而 TodoWrite 用于会话内实时协调。

Core contracts

核心契约

First read routing and select the route from the leading argument of
```
/team
```
before any setup or worktree.

Walk this phase table in order:

Worktree → Question → Research → Design → Structure → Plan → Implement → Code review → Security review → PR

There are no mid-run human gates. Continue until the draft PR exists.
For a picked-up ticket, read tracking rules and move the ticket to in-progress. At PR creation, use the same reference for the in-review transition and the multi-repo home-only closing rule.
Before WORKTREE, run the non-blocking probes in
```
scripts/preflight.sh
```
; no result blocks the run.
Read design reviewer brief and dispatch its review brief with the artifact directory substituted and the paths named at the top of the design review gate reference attached.
Read
```
references/15-host-dispatch.md
```
before the first dispatch and resolve every agent through it.
In multi-repo mode, use
```
4-repos.md
```
; see Multi-repo topics in the Rules reference.
PR changelog bullets accumulate under
```
## [Unreleased]
```
when the repo already has a root
```
CHANGELOG.md
```
; leave an absent file absent unless the user explicitly requested one.

首先阅读路由规则，并在执行任何 setup 或 worktree 操作之前，根据
```
/team
```
的 leading argument 选择 route。

按顺序执行以下阶段表：

Worktree → Question → Research → Design → Structure → Plan → Implement → Code review → Security review → PR

。

运行过程中没有中途人工门禁。持续执行，直到 draft PR 存在。
领取 ticket 后，阅读跟踪规则，并将 ticket 移至 in-progress。创建 PR 时，使用同一引用文档完成 in-review 状态转换，并遵循仅在 home 仓库中关闭的多仓库规则。
在 WORKTREE 之前，运行
```
scripts/preflight.sh
```
中的非阻塞探针；任何结果都不会阻止运行。
阅读设计评审者简报，派发其评审简报，替换 artifact 目录，并附加设计评审门禁引用文档顶部列出的路径。
在首次派发之前阅读
```
references/15-host-dispatch.md
```
，并通过该文档解析每个 Agent。
在多仓库模式下，使用
```
4-repos.md
```
；参阅规则引用文档中的多仓库主题。
当仓库已有根目录
```
CHANGELOG.md
```
时，PR changelog 条目应累积到
```
## [Unreleased]
```
下；如果文件不存在，则保持其不存在，除非用户明确要求创建。

Procedure references

流程引用

Read each reference completely when reaching that stage, in order; later stages depend on state and gates established earlier.

Routing
Setup
The Phase Loop
Where a phase agent's output lives
Orchestrator-Emit Gate (leading worktree)
Design Review Gate (design)
Orchestrator-Emit Gate (post-design-review secondary worktrees)
Mechanical Gate (test confirmation)
Orchestrator-Emit Gate (PR / ship)
Rules
Host-neutral agent dispatch

到达相应阶段时，按顺序完整阅读每个引用文档；后续阶段依赖先前阶段已建立的状态和门禁。

路由
初始化
阶段循环
阶段 Agent 输出的存放位置
Orchestrator-Emit 门禁（leading worktree）
设计评审门禁（design）
Orchestrator-Emit 门禁（设计评审后的次要 worktrees）
机械门禁（测试确认）
Orchestrator-Emit 门禁（PR / ship）
规则
宿主中立的 Agent 调度

Applied principles

应用原则

Read and apply: focused work rules, verified results rules, durable state rules, boil the ocean rules, and execution rules.

阅读并应用：聚焦工作规则、已验证结果规则、持久状态规则、boil the ocean 规则，以及执行规则。