get-shit-done/commands/gsd/spec-phase.md at b1a670e662fdae35945d9d8dfc74008aaa9dfc85

mirror of https://github.com/glittercowboy/get-shit-done synced 2026-04-25 17:25:23 +02:00

Files

Tom Boucher b1a670e662 fix(#2697 ): replace retired /gsd: prefix with /gsd- in all user-facing text (#2699 )

All workflow, command, reference, template, and tool-output files that
surfaced /gsd:<cmd> as a user-typed slash command have been updated to
use /gsd-<cmd>, matching the Claude Code skill directory name.

Closes #2697

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-04-25 10:59:33 -04:00

2.6 KiB

Raw Blame History

name, description, argument-hint, allowed-tools

name

description

argument-hint

allowed-tools

gsd:spec-phase

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.

<phase> [--auto] [--text]

Read

Write

Bash

Glob

Grep

AskUserQuestion

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"

<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>

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.

Execute the spec-phase workflow from @~/.claude/get-shit-done/workflows/spec-phase.md 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.

<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>

2.6 KiB Raw Blame History

2.6 KiB

Raw Blame History