gsd-spec-phase

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

<objective> Clarify phase requirements through structured Socratic questioning with quantitative ambiguity scoring.

Position in workflow:

spec-phase → discuss-phase → plan-phase → execute-phase → verify

How it works:

Load phase context (PROJECT.md, REQUIREMENTS.md, ROADMAP.md, STATE.md)
Scout the codebase — understand current state before asking questions
Run Socratic interview loop (up to 6 rounds, rotating perspectives)
Score ambiguity across 4 weighted dimensions after each round
Gate: ambiguity ≤ 0.20 AND all dimensions meet minimums → write SPEC.md
Commit SPEC.md — discuss-phase picks it up automatically on next run

Output:

{phase_dir}/{padded_phase}-SPEC.md

— falsifiable requirements that lock "what/why" before discuss-phase handles "how" </objective>

<execution_context> @~~/.claude/gsd-core/workflows/spec-phase.md @~~/.claude/gsd-core/templates/spec.md </execution_context>

<runtime_note> Copilot (VS Code): Use

vscode_askquestions

wherever this workflow calls

AskUserQuestion

. They are equivalent. </runtime_note>

<context> Phase number: $ARGUMENTS (required)

Flags:

```
--auto
```
— Skip interactive questions; Claude selects recommended defaults and writes SPEC.md
```
--text
```
— Use plain-text numbered lists instead of TUI menus (required for
```
/rc
```
remote sessions)

Context files are resolved in-workflow using

init phase-op

. </context>

<process> Execute end-to-end.

MANDATORY: Read the workflow file BEFORE taking any action. The workflow contains the complete step-by-step process including the Socratic interview loop, ambiguity scoring gate, and SPEC.md generation. Do not improvise from the objective summary above. </process>

<success_criteria>

Codebase scouted for current state before questioning begins
All 4 ambiguity dimensions scored after each interview round
Gate passed: ambiguity ≤ 0.20 AND all dimension minimums met
SPEC.md written with falsifiable requirements, explicit boundaries, and acceptance criteria
SPEC.md committed atomically
User knows they can now run /gsd-discuss-phase which will load SPEC.md automatically </success_criteria>

<objective> 通过结构化的苏格拉底式提问和量化歧义评分来明确阶段需求。

在工作流中的位置：

spec-phase → discuss-phase → plan-phase → execute-phase → verify

工作原理：

加载阶段上下文（PROJECT.md、REQUIREMENTS.md、ROADMAP.md、STATE.md）
探查代码库——在提问前了解当前状态
运行苏格拉底式访谈循环（最多6轮，轮换视角）
每轮后从4个加权维度对歧义进行评分
准入条件：歧义评分≤0.20 且所有维度达到最低要求 → 编写SPEC.md
提交SPEC.md——讨论阶段在下次运行时会自动获取该文件

输出：

{phase_dir}/{padded_phase}-SPEC.md

——可证伪的需求，在讨论阶段处理“如何做”之前锁定“做什么/为什么做” </objective>

<execution_context> @~~/.claude/gsd-core/workflows/spec-phase.md @~~/.claude/gsd-core/templates/spec.md </execution_context>

<runtime_note> Copilot (VS Code)： 当工作流调用

AskUserQuestion

时，使用

vscode_askquestions

替代。二者功能等效。 </runtime_note>

<context> 阶段编号：$ARGUMENTS（必填）

标志：

```
--auto
```
——跳过交互式提问；Claude选择推荐默认值并编写SPEC.md
```
--text
```
——使用纯文本编号列表替代TUI菜单（/rc远程会话必填）

上下文文件通过

init phase-op

在工作流中解析。 </context>

<process> 端到端执行。

强制要求： 在采取任何行动前先阅读工作流文件。工作流包含完整的分步流程，包括苏格拉底式访谈循环、歧义评分准入条件和SPEC.md生成逻辑。请勿仅根据上述目标摘要自行发挥。 </process>

<success_criteria>

在提问开始前已探查代码库当前状态
每轮访谈后对所有4个歧义维度进行评分
通过准入条件：歧义评分≤0.20 且所有维度达到最低要求
编写的SPEC.md包含可证伪需求、明确边界和验收标准
SPEC.md已原子提交
用户知晓现在可以运行/gsd-discuss-phase，该命令会自动加载SPEC.md </success_criteria>