gsd-spec-phase

To turn phase intent into an unambiguous specification, you run a structured Socratic questioning loop that quantifies ambiguity across four dimensions. It generates a falsifiable SPEC.md that locks down deliverables and acceptance criteria before development proceeds.

Socratic questioning with ambiguity scoring is a structured interview loop that asks up to six rounds of rotating-perspective questions to clarify deliverables. It quantifies ambiguity after each round to ensure requirements meet a strict threshold before workflow progression.

You prevent guess-based downstream work by applying spec-gated workflow progression that only writes a committed SPEC.md when ambiguity scoring drops to 0.20 or below. This ensures all minimum dimension thresholds are met before the next phase begins.

Yes, the specification process scans the current repository state before asking questions to ensure the generated SPEC.md reflects real constraints and facts. This codebase-aware approach grounds the Socratic interview in actual project conditions.

After the SPEC.md is committed, the workflow automatically hands off to the discuss-phase. The subsequent discuss-phase loads the committed specification on the next run to focus entirely on determining how to execute the locked deliverables.

You should use automated specification generation after the codebase is first scouted and context files are loaded, but before the discuss-phase begins. It is required when you need to define phase deliverables with quantitative ambiguity scoring before execution.