gsd:spec-phase
GitHub通过苏格拉底式提问和量化模糊度评分,在实施前澄清阶段需求并生成SPEC.md。确保需求可证伪且边界明确,为后续讨论阶段提供锁定目标。
Trigger Scenarios
Install
npx skills add davepoon/buildwithclaude --skill gsd:spec-phase -g -y
SKILL.md
Frontmatter
{
"name": "gsd:spec-phase",
"description": "Socratic spec refinement — clarify WHAT a phase delivers with ambiguity scoring before discuss-phase. Produces a SPEC.md with falsifiable requirements locked before implementation decisions begin.",
"allowed-tools": [
"Read",
"Write",
"Bash",
"Glob",
"Grep",
"AskUserQuestion"
],
"argument-hint": "<phase> [--auto] [--text]"
}
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"
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/spec-phase.md @${CLAUDE_PLUGIN_ROOT}/templates/spec.md </execution_context>
<runtime_note>
Copilot (VS Code): Use vscode_askquestions wherever this workflow calls AskUserQuestion. They are equivalent.
</runtime_note>
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/rcremote sessions)
Context files are resolved in-workflow using init phase-op.
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.
<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>
Version History
- 502fc01 Current 2026-07-05 15:15


