Back to Details

workbench-gsd-tasking

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Workbench GSD Tasking

Workbench GSD 任务管理

Use this skill to turn approved requirements, product designs, or technical designs into executable tasks.

使用此技能将已获批的需求、产品设计或技术设计转化为可执行任务。

Tasking Standard

任务管理标准

Each task has one owner, one outcome, one evidence requirement, and one verification path.
Parallelize only when write scopes or live mutation surfaces are clearly separate.
Put approval gates before live mutations, destructive changes, external posts, billing changes, or broad binding updates.
Include rollback or recovery evidence for live resource updates.
Keep smoke tests separate when they depend on committed source or synchronized live state.

每个任务对应一名负责人、一个预期成果、一项证据要求和一条验证路径。
仅当写入范围或实时变更面明确分离时，才可并行执行任务。
在执行实时变更、破坏性修改、外部发布、计费变更或广泛绑定更新前，需设置审批节点。
针对实时资源更新，需包含回滚或恢复的相关证据。
若冒烟测试依赖已提交的源码或同步的实时状态，则需单独执行。

Task Shape

任务结构

For each task, include:

```
ID
```
```
OWNER
```
```
OBJECTIVE
```
```
SCOPE
```
```
NON-GOALS
```
```
INPUTS
```
```
OUTPUT
```
```
VERIFICATION
```
```
ROLLBACK
```
```
DEPENDENCIES
```

每个任务需包含以下内容：

```
ID
```
```
OWNER
```
```
OBJECTIVE
```
```
SCOPE
```
```
NON-GOALS
```
```
INPUTS
```
```
OUTPUT
```
```
VERIFICATION
```
```
ROLLBACK
```
```
DEPENDENCIES
```

Output Contract

输出规范

Return:

```
TASKS
```
: ordered
```
T1
```
,
```
T2
```
,
```
T3
```
list.
```
GATES
```
: approval or review points.
```
PARALLELISM
```
: what can run concurrently and what must serialize.
```
FINAL SMOKE
```
: end-to-end check.
```
CLOSEOUT
```
: docs, comments, commits, and residual risks.

返回内容需包含：

```
TASKS
```
：按顺序排列的
```
T1
```
、
```
T2
```
、
```
T3
```
任务列表。
```
GATES
```
：审批或评审节点。
```
PARALLELISM
```
：可并行执行与必须串行执行的任务说明。
```
FINAL SMOKE
```
：端到端检查。
```
CLOSEOUT
```
：文档、注释、提交记录及剩余风险说明。