pdd-feature

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

PDD feature

PDD 功能

One chat per area. Briefs:

steps/

= optional.

story: understand, visual?, prompt-story → gate: approve
prompt-pr: check, try? → approve, then gate: pr (PR 1: prompt, Story, tests), then ask
code: build, verify, formal → gate: pr (PR 2)

每个领域单独使用一个聊天。步骤简报：

steps/

。

表示可选。

story：理解、visual?、prompt-story → gate：approve
prompt-pr：检查、try? → approve，然后 gate：pr（PR 1：prompt、Story、测试），然后询问用户
code：构建、验证、formal → gate：pr（PR 2）

Rules

规则

The main chat coordinates with the person. It writes no code.
Run each step in a new subagent, never reused, so verify never checks its own code. Give it its full brief at once: the step file and file paths, not the chat history. Then wait for it with one long time-out. Do not send small follow-up messages or use short waits.
At a gate, show the result, ask the person, and stop. For changes, revise here and ask again.
Write each link as its full URL (
```
https://…
```
), never as a linked word.
Before an optional step, ask the person and wait for the answer: "Do you want a visual design step? yes/no". In a run, run
```
<pdd> workflow ask
```
first. For a page or a screen, recommend visual: it makes the app map.
At the story gate, give the full paths of the Story files and the plan, and show the plan list. The person can say "make it one Story", "split part 5" or "change Story 5: …". A change request names a Story: redo only that Story and its test file. If a new prompt covers only this issue, say that a bigger "adopt PDD for this module" step can come later. You may offer: "You can also open it now with
```
pdd try <story>
```
before the check." If visual made an app map, tell the person to run
```
pdd try <story> --new
```
. End with: "Reply 'I approve' here or run
```
pdd workflow approve N
```
, or tell me what to change."
Before PR 1, show one
```
Runtime check
```
line per Story with its report link, and the Try links, if any. Ask the person to try it and approve, or ask for changes. pdd opens PR 1 only after the approval. Then show the PR 1 link and ask: "Do you want the code PR now, or stop here and merge PR 1 first? To make the code PR later, run
```
pdd workflow approve N
```
." The code area starts only when the person asks.
If verify or formal finds a failing case, go back to build in a new subagent, at most 2 times. If it still fails, PR 2 opens anyway with "✗ N vectors fail" on top. Say so at the gate.
A person decides expected values. Never change a test to make it pass.
Never push, open a PR or merge.

主聊天负责与用户协调，不编写代码。
每个步骤都在一个新的 subagent 中运行，且不得复用，这样 verify 就不会检查自己编写的代码。一次性向它提供完整简报：步骤文件和文件路径，而不是聊天历史。随后使用一次长时间超时等待其完成。不要发送简短的后续消息，也不要使用短时等待。
在 gate 处展示结果，询问用户，然后停止。需要修改时，在此修订并再次询问。
每个链接都写成完整 URL（
```
https://…
```
），绝不能只显示带链接的文字。
在可选步骤之前，询问用户并等待回答：“是否需要 visual design 步骤？yes/no”。在 run 中，先运行
```
<pdd> workflow ask
```
。对于页面或屏幕，建议选择 visual，因为它会生成 app map。
在 story gate 处，给出所有 Story 文件的完整路径和计划，并展示计划列表。用户可以说“合并为一个 Story”“拆分第 5 部分”或“修改 Story 5：……”。变更请求必须指定一个 Story：只重做该 Story 及其测试文件。如果新的 prompt 仅涉及此问题，应说明之后还可以执行范围更大的“adopt PDD for this module”步骤。还可以提示：“你也可以在检查前使用
```
pdd try <story>
```
立即打开它。”如果 visual 已生成 app map，则告知用户运行
```
pdd try <story> --new
```
。最后提示：“在此回复
```
I approve
```
，或运行
```
pdd workflow approve N
```
，或者告诉我需要修改什么。”
在 PR 1 之前，针对每个 Story 显示一行
```
Runtime check
```
，并附上报告链接；如果有 Try 链接，也一并显示。请用户试用并批准，或提出修改。只有获得批准后，pdd 才会创建 PR 1。然后显示 PR 1 链接并询问：“现在要创建代码 PR，还是先停在这里并合并 PR 1？如果稍后创建代码 PR，请运行
```
pdd workflow approve N
```
。”只有用户提出要求后，代码区域才会启动。
如果 verify 或 formal 发现失败用例，则返回 build 步骤，在新的 subagent 中执行，最多重试 2 次。如果仍然失败，PR 2 仍会创建，并在顶部显示“✗ N vectors fail”。在 gate 处说明这一情况。
预期值由用户决定。绝不通过修改测试来使其通过。
绝不 push、创建 PR 或 merge。

In a run (see the first message)

在 run 中（参见第一条消息）

Each step writes notes to
```
<run folder>/STEP.md
```
and commits its code.
When you need the person's answer in the middle of a step, run
```
<pdd> workflow ask "<question>"
```
first. Then ask it in a plain chat message (never a question dialog such as request_user_input) and end your turn. The person answers in the chat or with
```
pdd workflow changes N "answer"
```
.
When the person approves in their own words, run
```
<pdd> workflow approve N
```
. Never approve for them.

每个步骤都将说明写入
```
<run folder>/STEP.md
```
，并提交其代码。
步骤中途需要用户回答时，先运行
```
<pdd> workflow ask "<question>"
```
。然后通过普通聊天消息提问（绝不使用 request_user_input 之类的问题对话框），并结束当前轮次。用户可以在聊天中回答，或运行
```
pdd workflow changes N "answer"
```
。
当用户用自己的措辞表示批准时，运行
```
<pdd> workflow approve N
```
。绝不代用户批准。