workbench-goal-mode

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Workbench Goal Mode

Workbench 目标模式

Use this skill when an issue contains

/goal

GOAL_MODE: yes

, asks for full autonomous completion, or asks an agent to keep working until a concrete outcome is achieved.

Goal Mode is an execution wrapper, not a permission override. It keeps the objective alive across turns, reruns, local fixes, and partial evidence, while preserving existing approval, safety, and review gates.

当工单中包含

/goal

、

GOAL_MODE: yes

，要求完全自主完成，或要求Agent持续工作直至达成具体结果时，使用此技能。

目标模式是一种执行封装，而非权限覆盖。它能让目标在多轮交互、重新运行、本地修复和部分验证过程中保持有效，同时保留现有的审批、安全和审核机制。

Activation

激活方式

Before changing files or live resources, post a compact lock:

text

GOAL_LOCK:
objective:
owner:
non_goals:
closeout_gates:
operator_call_conditions:

```
objective
```
is the user-visible outcome, not a task list.
```
owner
```
is one assigned agent or human owner.
```
non_goals
```
prevents the agent from expanding into adjacent work.
```
closeout_gates
```
names the evidence required before claiming done.
```
operator_call_conditions
```
names the few cases where human input is needed.

在修改文件或在线资源前，发布一个简洁的锁定声明：

text

GOAL_LOCK:
objective:
owner:
non_goals:
closeout_gates:
operator_call_conditions:

```
objective
```
是用户可见的结果，而非任务列表。
```
owner
```
是指定的Agent或负责人。
```
non_goals
```
用于防止Agent将工作扩展到相邻领域。
```
closeout_gates
```
列出宣告完成前所需的验证依据。
```
operator_call_conditions
```
列出需要人工介入的少数场景。

Execution Rules

执行规则

Build a checklist from the locked goal, then execute it.
Do not stop after a local fix if the broader goal remains unverified.
When a command, build, test, or smoke fails, investigate and repair before asking for help.
Treat repeated identical failures as a mechanism problem: change the probe or report the exact blocker instead of retrying the same action.
Use fresh reruns when context is stale, repo state changed, auth changed, or the previous run was bound to the wrong repo/resource.
Preserve issue-level scope, approval gates, secrets boundaries, and runtime ownership.
```
/goal
```
does not permit destructive cleanup, force pushes, hidden live mutations, broad repo reads, or credential handling.

根据锁定的目标构建检查清单，然后执行。
如果更宏观的目标尚未验证，请勿在本地修复后停止工作。
当命令、构建、测试或冒烟测试失败时，先调查并修复，再请求帮助。
将重复出现的相同故障视为机制问题：更改排查方式，或报告确切的阻塞点，而非重复执行相同操作。
当上下文过期、仓库状态变更、权限变更，或上一次运行绑定到错误的仓库/资源时，重新执行任务。
保留工单级别的范围、审批机制、密钥边界和运行时所有权。
```
/goal
```
不允许进行破坏性清理、强制推送、隐藏的在线变更、大范围仓库读取或凭证处理。

Required Closeout Gates

必需的收尾校验机制

For code, ops, or workflow-changing tasks, address every relevant gate before claiming completion:

```
build
```
: documented build or closest real startup/build smoke.
```
test
```
: targeted tests plus the smallest meaningful regression check.
```
help_smoke
```
: CLI help, startup, UI load, or endpoint smoke when command/user surfaces changed.
```
docs_report
```
: docs, changelog, handoff, or explicit "not needed" rationale.
```
git_status
```
: clean state or intentionally explained dirty state.
```
evidence
```
: exact commands, files, links, screenshots, issue IDs, run IDs, or artifact paths.

If a gate does not apply, say why. A skipped gate without rationale is

FLAG

对于代码、运维或工作流变更任务，在宣告完成前需满足所有相关校验要求：

```
build
```
：已记录的构建过程或最接近真实环境的启动/构建冒烟测试。
```
test
```
：针对性测试加上最小范围的有意义回归检查。
```
help_smoke
```
：当命令/用户界面变更时，需进行CLI帮助、启动、UI加载或端点冒烟测试。
```
docs_report
```
：文档更新、变更日志、交接说明，或明确的“无需更新”理由。
```
git_status
```
：干净的仓库状态，或对故意保留的脏状态做出解释。
```
evidence
```
：确切的命令、文件、链接、截图、工单ID、运行ID或工件路径。

如果某条校验不适用，请说明原因。未说明理由就跳过校验将标记为

FLAG

。

Operator Call Conditions

人工介入条件

Call the operator only for true external blockers:

missing credentials or approval that cannot be inferred from the issue;
unavailable third-party service or remote host;
destructive or irreversible operation approval;
repo/resource access failure that cannot be fixed inside the assigned context;
requirement conflict where continuing would change the user's goal.

The blocker report must include attempted fixes, exact evidence, and the smallest operator action needed.

仅在遇到真正的外部阻塞时才联系操作人员：

工单中无法推断的缺失凭证或审批；
第三方服务或远程主机不可用；
需要审批的破坏性或不可逆操作；
在指定上下文内无法修复的仓库/资源访问失败；
需求冲突，继续执行会改变用户目标。

阻塞报告必须包含已尝试的修复措施、确切依据，以及所需的最小操作。

Closeout Contract

收尾协议

Use this scaffold:

text

GOAL_LOCK:
WHAT_CHANGED:
VERIFICATION:
DOCS_REPORT:
GIT_STATUS:
RESIDUAL_RISK:
OPERATOR_NEEDED: yes/no
VERDICT: PASS | FLAG | BLOCK

PASS

means the locked objective is achieved and every relevant closeout gate has evidence.

FLAG

means useful progress remains reviewable but a gate or risk is unresolved.

BLOCK

means the objective cannot be safely completed without an operator or upstream fix.

使用以下模板：

text

GOAL_LOCK:
WHAT_CHANGED:
VERIFICATION:
DOCS_REPORT:
GIT_STATUS:
RESIDUAL_RISK:
OPERATOR_NEEDED: yes/no
VERDICT: PASS | FLAG | BLOCK

PASS

表示锁定的目标已达成，且所有相关收尾校验均有依据。

FLAG

表示已取得有用进展可供审核，但存在未解决的校验项或风险。

BLOCK

表示若没有操作人员或上游修复，目标无法安全完成。