Back to Details

closing-ritual

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Closing ritual

收尾流程

Run once, after a diff exists and before presenting work as done. Skip trivial changes (typo, one-liner) — a forced report there invents flaws.
Leading words: doubts, blind spots, unverified.
在差异存在且工作尚未提交验收前执行一次。跳过微小改动（如拼写错误、单行代码修改）——强制对此类内容生成报告会凭空捏造问题。
核心关键词： 疑问、盲区、未验证内容。

Steps

步骤

1. Interrogate

1. 自查

  1. What am I least confident about in what I just did? — doubts: things glossed over or quietly assumed instead of asked.
  2. What is the user probably missing that they haven't thought to ask? — blind spots: "you asked for X, but Y bites later."
  3. What did I claim works without running or verifying it? — the unverified.
Done when: every answer traces to evidence — a file:line, a command not run, an assumption made without asking — or is cut.
  1. 我对刚完成的工作中哪部分最没信心？——疑问：那些被一笔带过或未经确认就默认的内容。
  2. 用户可能忽略了哪些他们没想到要问的内容？——盲区：比如“你要求做X，但Y会在后续引发问题”。
  3. 我声称可行但未实际运行或验证的内容是什么？——未验证内容。
完成标准： 每个答案都有对应的依据——如某文件的某一行、未执行的命令、未确认的假设——否则就删除该答案。

2. Report

2. 汇报

markdown
undefined
markdown
undefined

Doubts

Doubts

  • <claim> — <why unsure> — <evidence> (or: Nothing)
  • <claim> — <why unsure> — <evidence> (or: Nothing)

Blind spots

Blind spots

  • <context> — <why it matters later> (or: Nothing)
  • <context> — <why it matters later> (or: Nothing)

Unverified

Unverified

  • <claim> — <what would verify it> (or: Nothing)

Report only; the user decides what gets fixed. Large or risky diffs go to
review-core / review-tribunal instead.

**Done when:** every listed item carries evidence; empty sections say "Nothing".
  • <claim> — <what would verify it> (or: Nothing)

仅需汇报；由用户决定需要修复的内容。大型或高风险的差异应提交至review-core / review-tribunal（核心评审/评审委员会）处理。

**完成标准：** 每个列出的条目都带有依据；无内容的部分需标注“无”。