Name: gsd:spec-phase
Author: AdarBahar

Prompt file imported from AdarBahar/groovy (.claude/commands/gsd/spec-phase.md). Fill in {{arguments}} before use. Copyright stays with the author.

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> @/Users/adar/Code/groovy/.claude/get-shit-done/workflows/spec-phase.md @/Users/adar/Code/groovy/.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>

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.

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>

<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> @/Users/adar/Code/groovy/.claude/get-shit-done/workflows/spec-phase.md @/Users/adar/Code/groovy/.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:** - `--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>

{ "prompt": "<objective>\nClarify phase requirements through structured Socratic questioning with quantitative ambiguity scoring.\n\n**Position in workflow:** `spec-phase → discuss-phase → plan-phase → execute-phase → verify`\n\n**How it works:**\n1. Load phase context (PROJECT.md, REQUIREMENTS.md, ROADMAP.md, STATE.md)\n2. Scout the codebase — understand current state before asking questions\n3. Run Socratic interview loop (up to 6 rounds, rotating perspectives)\n4. Score ambiguity across 4 weighted dimensions after each round\n5. Gate: ambiguity ≤ 0.20 AND all dimensions meet minimums → write SPEC.md\n6. Commit SPEC.md — discuss-phase picks it up automatically on next run\n\n**Output:** `{phase_dir}/{padded_phase}-SPEC.md` — falsifiable requirements that lock \"what/why\" before discuss-phase handles \"how\"\n</objective>\n\n<execution_context>\n@/Users/adar/Code/groovy/.claude/get-shit-done/workflows/spec-phase.md\n@/Users/adar/Code/groovy/.claude/get-shit-done/templates/spec.md\n</execution_context>\n\n<runtime_note>\n**Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`. They are equivalent.\n</runtime_note>\n\n<context>\nPhase number: {{arguments}} (required)\n\n**Flags:**\n- `--auto` — Skip interactive questions; Claude selects recommended defaults and writes SPEC.md\n- `--text` — Use plain-text numbered lists instead of TUI menus (required for `/rc` remote sessions)\n\nContext files are resolved in-workflow using `init phase-op`.\n</context>\n\n<process>\nExecute end-to-end.\n\n**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.\n</process>\n\n<success_criteria>\n- Codebase scouted for current state before questioning begins\n- All 4 ambiguity dimensions scored after each interview round\n- Gate passed: ambiguity ≤ 0.20 AND all dimension minimums met\n- SPEC.md written with falsifiable requirements, explicit boundaries, and acceptance criteria\n- SPEC.md committed atomically\n- User knows they can now run /gsd-discuss-phase which will load SPEC.md automatically\n</success_criteria>", "variables": [ "arguments" ], "notes": "Clarify WHAT a phase delivers with ambiguity scoring; produces a SPEC.md before discuss-phase. Tools: Read, Write, Bash, Glob, Grep, AskUserQuestion. Arguments: <phase> [--auto] [--text].", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/AdarBahar/groovy", "path": ".claude/commands/gsd/spec-phase.md", "ref": "1536eacbdd17ea203e6ba5b326e29c5228bd80cf", "url": "https://github.com/AdarBahar/groovy/blob/1536eacbdd17ea203e6ba5b326e29c5228bd80cf/.claude/commands/gsd/spec-phase.md", "key": "AdarBahar/groovy/.claude/commands/gsd/spec-phase.md" } } }

gsd:spec-phase

About

Use it

Manifest

Reviews