goal-contract-writer

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Goal Contract Writer

Overview

概述

goal-contract-writer

turns ambiguous work into a standard Goal Contract.

Clarify only what is required to define the work. Then return the canonical contract. Conversation is not the product.

This skill does not implement, run, or manage a Goal-Driven agent loop. It defines the upstream contract that a loop, workflow engine, host goal system, or human operator can execute and verify.

goal-contract-writer

is the only normal user-facing entrypoint. The paired

goal-contract-verifier

skill exists for runtimes or operators that need fresh-subagent verification of execution state, but verifier behavior is not part of this skill's required output.

goal-contract-writer

可将模糊的工作内容转化为标准的Goal Contract。

仅明确定义工作所需的内容，然后返回标准合约，无需多余对话。

该技能不实现、运行或管理目标驱动型Agent循环，而是定义上游合约，供循环系统、工作流引擎、宿主目标系统或人工操作者执行和验证。

goal-contract-writer

是唯一面向普通用户的入口。配套的

goal-contract-verifier

技能供运行时或操作者使用，用于对执行状态进行全新子Agent验证，但验证器的行为不属于本技能的必填输出内容。

When to Use

使用场景

Use this skill when:

the request has a concrete outcome but starts ambiguous
the next agent, system, or person needs a stable goal artifact
success must be judged by observable evidence

Do not use it for open-ended ideation or as a replacement for execution workflows.

在以下场景中使用本技能：

请求有明确的结果，但初始表述模糊
下一级Agent、系统或人员需要一个稳定的目标工件
成功与否必须通过可观察的依据来判断

请勿将其用于开放式构思，或作为执行工作流的替代方案。

Core Output

核心输出

Produce exactly one canonical artifact:

```
Goal Contract
```

Goal Contract

must contain exactly these fields:

```
goal
```
```
scope
```
```
success_criteria
```
```
evidence
```
```
guardrails
```

Do not add runtime verdicts, adapter metadata, or workflow prose to the contract body.

Use

references/canonical-goal-contract.md

for the canonical contract schema.

生成且仅生成一个标准工件：

```
Goal Contract
```

Goal Contract

必须包含以下字段：

```
goal
```
（目标）
```
scope
```
（范围）
```
success_criteria
```
（成功标准）
```
evidence
```
（验证依据）
```
guardrails
```
（约束规则）

请勿在合约主体中添加运行时结论、适配器元数据或工作流描述性文字。

请参考

references/canonical-goal-contract.md

获取标准合约 schema。

Contract Generation Flow

合约生成流程

Clarify until
```
goal
```
and
```
scope
```
can be written without guesswork.
Write
```
success_criteria
```
that fully cover the
```
goal
```
and can be checked without subjective judgment.
Write matching
```
evidence
```
that proves or disproves each criterion without adding hidden acceptance rules.
Record
```
guardrails
```
that prevent scope drift, unsafe assumptions, or missing approvals.
Return the canonical Goal Contract and stop.

Use

references/contract-elicitation-protocol.md

for clarification rules and

examples/

for concrete model contracts.

进行澄清，直到无需猜测即可写出
```
goal
```
和
```
scope
```
。
编写
```
success_criteria
```
，需完全覆盖
```
goal
```
，且可通过客观判断进行检查。
编写匹配的
```
evidence
```
，用于证明或否定每条标准，且不得隐含未明确的验收规则。
记录
```
guardrails
```
，防止范围漂移、不安全假设或遗漏审批。
返回标准Goal Contract并停止操作。

请参考

references/contract-elicitation-protocol.md

获取澄清规则，参考

examples/

获取具体的合约示例。

Hard Rules

硬性规则

Do not replace the contract with free-form advice or host-specific prose.
Do not use subjective completion language.
Do not add verifier workflow, execution routing, owners, priorities, or next steps to the canonical contract.
Do not let
```
evidence
```
smuggle in acceptance rules that are missing from
```
success_criteria
```
.
Do not let any adapter redefine the canonical contract fields.
Do not continue into planning or execution unless the user explicitly starts a separate task.
Keep the contract execution-neutral.

不得用自由形式的建议或特定宿主的描述性文字替代合约。
不得使用主观性的完成类表述。
不得在标准合约中添加验证器工作流、执行路由、负责人、优先级或后续步骤。
不得让
```
evidence
```
隐含
```
success_criteria
```
中未提及的验收规则。
不得允许任何适配器重新定义标准合约的字段。
除非用户明确启动单独任务，否则不得进入规划或执行阶段。
保持合约与执行无关。

Downstream Consumption

下游消费

Downstream systems consume the contract after this skill defines it.

A host-native goal system may use it as durable input.
A workflow system may use it for planning, execution, verification, or review.
A specification system may use it for persistent spec or task assets.
A human operator may execute directly from it.
Adapter-specific routing, ownership, runtime state, or verifier artifacts belong outside the canonical contract.
Runtimes or operators may invoke the paired
```
goal-contract-verifier
```
to verify execution state, but that verification flow does not change what
```
goal-contract-writer
```
returns.

Use

references/downstream-adapters.md

for adapter rules and examples.

下游系统会在本技能定义合约后使用该合约。

宿主原生目标系统可将其作为持久化输入。
工作流系统可将其用于规划、执行、验证或审核。
规范系统可将其作为持久化规范或任务资产。
人工操作者可直接依据其执行任务。
适配器特定的路由、归属、运行时状态或验证器工件不属于标准合约范畴。
运行时或操作者可调用配套的
```
goal-contract-verifier
```
来验证执行状态，但该验证流程不会改变
```
goal-contract-writer
```
的返回内容。

请参考

references/downstream-adapters.md

获取适配器规则和示例。

References

参考资料

```
references/canonical-goal-contract.md
```

references/contract-elicitation-protocol.md

```
references/evidence-patterns.md
```
```
references/downstream-adapters.md
```
```
examples/README.md
```

```
references/canonical-goal-contract.md
```

references/contract-elicitation-protocol.md

```
references/evidence-patterns.md
```
```
references/downstream-adapters.md
```
```
examples/README.md
```

Resource Use

资源使用

Keep the canonical schema and pattern references in
```
references/
```
.
Keep complete before-and-after examples in
```
examples/
```
.
Keep interface metadata in
```
agents/
```
.

请将标准schema和模式参考文件放在
```
references/
```
目录下。
请将完整的前后示例放在
```
examples/
```
目录下。
请将接口元数据放在
```
agents/
```
目录下。