acceptance-orchestrator

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Acceptance Orchestrator

验收编排器

Overview

概述

Orchestrate coding work as a state machine that ends only when acceptance criteria are verified with evidence or the task is explicitly escalated.

Core rule: do not optimize for "code changed"; optimize for "DoD proven".

将编码工作作为状态机进行编排，仅当验收标准有证据验证通过或任务被明确升级时才会结束。

核心规则：不要为「代码变更」优化，要为「DoD 得到证实」优化。

Required Sub-Skills

所需子技能

```
create-issue-gate
```
```
closed-loop-delivery
```
```
verification-before-completion
```

Optional supporting skills:

```
deploy-dev
```
```
pr-watch
```
```
pr-review-autopilot
```
```
git-ship
```

```
create-issue-gate
```
```
closed-loop-delivery
```
```
verification-before-completion
```

可选支持技能：

```
deploy-dev
```
```
pr-watch
```
```
pr-review-autopilot
```
```
git-ship
```

Inputs

输入

Require these inputs:

issue id or issue body
issue status
acceptance criteria (DoD)
target environment (
```
dev
```
default)

Fixed defaults:

max iteration rounds =
```
2
```
PR review polling =
```
3m -> 6m -> 10m
```

需要以下输入项：

issue id 或 issue 内容
issue 状态
验收标准（DoD）
目标环境（默认
```
dev
```
）

固定默认值：

最大迭代轮次 =
```
2
```
PR 审查轮询间隔 =
```
3m -> 6m -> 10m
```

State Machine

状态机

```
intake
```
```
issue-gated
```
```
executing
```
```
review-loop
```
```
deploy-verify
```
```
accepted
```
```
escalated
```

```
intake
```
```
issue-gated
```
```
executing
```
```
review-loop
```
```
deploy-verify
```
```
accepted
```
```
escalated
```

Workflow

工作流

Intake
- Read issue and extract task goal + DoD.
Issue gate
- Use
```
create-issue-gate
```
  logic.
- If issue is not
```
ready
```
  or execution gate is not
```
allowed
```
  , stop immediately.
- Do not implement anything while issue remains
```
draft
```
  .
Execute
- Hand off to
```
closed-loop-delivery
```
  for implementation and local verification.
Review loop
- If PR feedback is relevant, batch polling windows as:
  - wait
```
3m
```
  - then
```
6m
```
  - then
```
10m
```
- After the
```
10m
```
  round, stop waiting and process all visible comments together.
Deploy and runtime verification
- If DoD depends on runtime behavior, deploy only to
```
dev
```
  by default.
- Verify with real logs/API/Lambda behavior, not assumptions.
Completion gate
- Before any claim of completion, require
```
verification-before-completion
```
  .
- No success claim without fresh evidence.

接收（Intake）
- 读取 issue 并提取任务目标 + DoD。
需求准入（Issue gate）
- 使用
```
create-issue-gate
```
  逻辑。
- 如果 issue 未处于
```
ready
```
  状态或执行准入未被
```
allowed
```
  ，立即停止。
- issue 仍为
```
draft
```
  状态时不要进行任何开发实现。
执行（Execute）
- 移交至
```
closed-loop-delivery
```
  进行开发实现和本地验证。
审查循环（Review loop）
- 如果 PR 反馈相关，按以下批次设置轮询等待窗口：
  - 等待
```
3m
```
  - 然后
```
6m
```
  - 然后
```
10m
```
- ```
10m
```
  轮询结束后，停止等待，统一处理所有可见评论。
部署与运行时验证（Deploy and runtime verification）
- 如果 DoD 依赖运行时行为，默认仅部署到
```
dev
```
  环境。
- 基于真实日志/API/Lambda行为进行验证，而非主观假设。
完成准入（Completion gate）
- 在声明完成前，必须执行
```
verification-before-completion
```
  。
- 无最新证据不得声明成功。

Stop Conditions

停止条件

Move to

accepted

only when every acceptance criterion has matching evidence.

Move to

escalated

when any of these happen:

DoD still fails after
```
2
```
full rounds
missing secrets/permissions/external dependency blocks progress
task needs production action or destructive operation approval
review instructions conflict and cannot both be satisfied

仅当所有验收标准都有对应的匹配证据时，才流转至

accepted

状态。

发生以下任意情况时流转至

escalated

状态：

2轮完整迭代后 DoD 仍未通过
缺少密钥/权限/外部依赖导致进度阻塞
任务需要生产环境操作或破坏性操作审批
审查指令存在冲突无法同时满足

Human Gates

人工准入

Always stop for human confirmation on:

prod/stage deploys beyond agreed scope
destructive git/data operations
billing or security posture changes
missing user-provided acceptance criteria

出现以下情况时必须停止并等待人工确认：

超出约定范围的生产/预发环境部署
破坏性 git/数据操作
账单或安全配置变更
缺少用户提供的验收标准

Output Contract

输出约定

When reporting status, always include:

```
Status
```
: intake / executing / accepted / escalated
```
Acceptance Criteria
```
: pass/fail checklist
```
Evidence
```
: commands, logs, API results, or runtime proof
```
Open Risks
```
: anything still uncertain
```
Need Human Input
```
: smallest next decision, if blocked

Do not report "done" unless status is

accepted

上报状态时必须包含：

```
Status
```
：intake / executing / accepted / escalated
```
Acceptance Criteria
```
：通过/失败检查清单
```
Evidence
```
：命令、日志、API 结果或运行时证明
```
Open Risks
```
：所有仍不确定的事项
```
Need Human Input
```
：如果阻塞，列出所需的最小下一步决策。

除非状态为

accepted

，否则不得上报「已完成」。