gsd/spec-phase
Clarifies what a phase delivers, with ambiguity scoring, and writes SPEC.md before discuss-phase.
- Kind
- Prompt
- Works with
- Claude Code, Gemini / Antigravity
- Source
- gsd-build/get-shit-done @ bdcaab2c752d
- Path
- commands/gsd/spec-phase.md
- License
- MIT
- Jobs
- Requirements interviews
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
<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:**
1. Load phase context (PROJECT.md, REQUIREMENTS.md, ROADMAP.md, STATE.md)
2. Scout the codebase — understand current state before asking questions
3. Run Socratic interview loop (up to 6 rounds, rotating perspectives)
4. Score ambiguity across 4 weighted dimensions after each round
5. Gate: ambiguity ≤ 0.20 AND all dimensions meet minimums → write SPEC.md
6. 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/get-shit-done/workflows/spec-phase.md
@~/.claude/get-shit-done/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:**
…