Back to Details

gm-complete

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

GM COMPLETE — Verification and Completion

GM 完成阶段——验证与收尾

You are in the VERIFY → COMPLETE phase. Files are written. Prove the whole system works end-to-end. Any new unknown = snake to 
planning
, restart chain.
GRAPH POSITION: 
PLAN → EXECUTE → EMIT → [VERIFY] → UPDATE-DOCS → COMPLETE
  • Entry: All EMIT gates passed. Entered from 
    gm-emit
    .
你处于验证→完成阶段。文件已编写完成，需证明整个系统可端到端正常运行。任何新出现的未知问题都将触发回溯至
planning
阶段，重启流程链。
流程位置：
PLAN → EXECUTE → EMIT → [VERIFY] → UPDATE-DOCS → COMPLETE
  • 进入条件：所有EMIT阶段的检查点已通过，从
    gm-emit
    阶段进入。

TRANSITIONS

流转规则

FORWARD:
  • .prd items remain → invoke 
    gm-execute
    skill (next wave)
  • .prd empty + feature work pushed → invoke 
    update-docs
    skill
BACKWARD:
  • Verification reveals broken file output → invoke 
    gm-emit
    skill, fix, re-verify, return
  • Verification reveals logic error → invoke 
    gm-execute
    skill, re-resolve, re-emit, return
  • Verification reveals new unknown → invoke 
    planning
    skill, restart chain
  • Verification reveals requirements wrong → invoke 
    planning
    skill, restart chain
TRIAGE on failure: broken file output → snake to 
gm-emit
| wrong logic → snake to 
gm-execute
| new unknown or wrong requirements → snake to 
planning
RULE: Any surprise = new unknown = snake to 
planning
. Never patch around surprises.
正向流转：
  • 若.prd文件仍有未完成项 → 调用
    gm-execute
    技能（下一轮执行）
  • .prd文件为空且功能代码已推送 → 调用
    update-docs
    技能
回溯流转：
  • 验证发现文件输出异常 → 调用
    gm-emit
    技能，修复后重新验证并返回当前阶段
  • 验证发现逻辑错误 → 调用
    gm-execute
    技能，重新解决问题、重新输出后返回当前阶段
  • 验证发现新的未知问题 → 调用
    planning
    技能，重启流程链
  • 验证发现需求有误 → 调用
    planning
    技能，重启流程链
失败分类处理：文件输出异常 → 回溯至
gm-emit
| 逻辑错误 → 回溯至
gm-execute
| 新未知问题或需求错误 → 回溯至
planning
规则：任何意外情况均视为新未知问题，需回溯至
planning
阶段。绝不能对意外情况进行临时补丁处理。

MUTABLE DISCIPLINE

可变约束检查

  • witnessed_e2e=UNKNOWN
    until real end-to-end run produces witnessed output
  • git_clean=UNKNOWN
    until 
    exec:bash\ngit status --porcelain
    returns empty
  • git_pushed=UNKNOWN
    until 
    exec:bash\ngit rev-list --count @{u}..HEAD
    returns 0
  • prd_empty=UNKNOWN
    until .prd has zero items
All four must resolve to KNOWN before COMPLETE. Any UNKNOWN = absolute barrier.
  • 在真实端到端运行产生可验证的输出前，
    witnessed_e2e
    状态为UNKNOWN
  • 在
    exec:bash\ngit status --porcelain
    返回空值前，
    git_clean
    状态为UNKNOWN
  • 在
    exec:bash\ngit rev-list --count @{u}..HEAD
    返回0前，
    git_pushed
    状态为UNKNOWN
  • 在.prd文件无未完成项前，
    prd_empty
    状态为UNKNOWN
完成阶段前，这四项状态必须全部变为KNOWN。任何一项为UNKNOWN都将视为绝对阻碍。

END-TO-END VERIFICATION

端到端验证

Run the real system with real data. Witness actual output.
NOT verification: docs updates, status text, saying done, screenshots alone, marker files.
exec:nodejs
const { fn } = await import('/abs/path/to/module.js');
console.log(await fn(realInput));
For browser/UI: invoke 
agent-browser
skill with real workflows. Server + client features require both exec:nodejs AND agent-browser. After every success: enumerate what remains — never stop at first green.
使用真实数据运行真实系统，验证实际输出结果。
以下行为不视为验证：更新文档、状态文本、口头宣称完成、仅截图、标记文件。
exec:nodejs
const { fn } = await import('/abs/path/to/module.js');
console.log(await fn(realInput));
针对浏览器/UI：调用
agent-browser
技能执行真实工作流。服务端+客户端功能需同时执行exec:nodejs和agent-browser验证。每次验证成功后，需列出剩余未完成项——绝不能在首次验证通过后就停止。

CODE EXECUTION

代码执行

exec:<lang> is the only way to run code. Bash tool body: 
exec:<lang>\n<code>
exec:nodejs
(default) | 
exec:bash
| 
exec:python
| 
exec:typescript
| 
exec:go
| 
exec:rust
| 
exec:java
| 
exec:deno
| 
exec:cmd
Only git in bash directly. Background tasks: 
exec:sleep\n<id>
, 
exec:status\n<id>
, 
exec:close\n<id>
. Runner: 
exec:runner\nstart|stop|status
. All activity visible in 
pm2 list
and 
pm2 monit
in user terminal.
exec:<语言>是唯一的代码运行方式。Bash工具格式：
exec:<语言>\n<代码内容>
exec:nodejs
（默认）| 
exec:bash
| 
exec:python
| 
exec:typescript
| 
exec:go
| 
exec:rust
| 
exec:java
| 
exec:deno
| 
exec:cmd
仅可在bash中直接执行git命令。后台任务：
exec:sleep\n<id>
、
exec:status\n<id>
、
exec:close\n<id>
。运行器：
exec:runner\nstart|stop|status
。所有活动均可在用户终端通过
pm2 list
和
pm2 monit
查看。

CODEBASE EXPLORATION

代码库探索

exec:codesearch
<natural language description>
exec:codesearch
<natural language description>

GIT ENFORCEMENT

Git强制规范

exec:bash
git status --porcelain
Must return empty.
exec:bash
git rev-list --count @{u}..HEAD
Must return 0. If not: stage → commit → push → re-verify. Local commit without push ≠ complete.
exec:bash
git status --porcelain
必须返回空值。
exec:bash
git rev-list --count @{u}..HEAD
必须返回0。若未返回0：暂存→提交→推送→重新验证。仅本地提交未推送不视为完成。

COMPLETION DEFINITION

完成定义

All of: witnessed end-to-end output | all failure paths exercised | .prd empty | git clean and pushed | 
user_steps_remaining=0
需同时满足以下所有条件：已验证端到端输出、已覆盖所有失败路径、.prd文件为空、Git仓库干净且已推送、
user_steps_remaining=0

CONSTRAINTS

约束规则

Never: claim done without witnessed output | uncommitted changes | unpushed commits | .prd items remaining | stop at first green | absorb surprises silently
Always: triage failure before snaking | witness end-to-end | snake to planning on any new unknown | enumerate remaining after every success
→ FORWARD: .prd items remain → invoke 
gm-execute
skill. → FORWARD: .prd empty + feature work pushed → invoke 
update-docs
skill. ↩ SNAKE to EMIT: file output wrong → invoke 
gm-emit
skill. ↩ SNAKE to EXECUTE: logic wrong → invoke 
gm-execute
skill. ↩ SNAKE to PLAN: new unknown or wrong requirements → invoke 
planning
skill, restart chain.
禁止行为：未验证输出就宣称完成、存在未提交的变更、存在未推送的提交、.prd文件仍有未完成项、首次验证通过后就停止、默默掩盖意外情况
必须行为：回溯前先分类处理失败、执行端到端验证、出现任何新未知问题时回溯至planning阶段、每次成功后列出剩余未完成项
→ 正向流转：.prd文件仍有未完成项 → 调用
gm-execute
技能。 → 正向流转：.prd文件为空且功能代码已推送 → 调用
update-docs
技能。 ↩ 回溯至EMIT：文件输出异常 → 调用
gm-emit
技能。 ↩ 回溯至EXECUTE：逻辑错误 → 调用
gm-execute
技能。 ↩ 回溯至PLAN：新未知问题或需求错误 → 调用
planning
技能，重启流程链。