gsd-spec-phase

Specification generation uses structured Socratic questioning to run up to six interview rounds, scoring ambiguity across four dimensions. This process transforms raw requirements into a falsifiable SPEC.md that defines what must be built and why before implementation begins.

Ambiguity scoring quantifies uncertainty across four dimensions after each Socratic interview round. It gates the specification workflow by requiring an ambiguity score of 0.20 or lower alongside minimum criteria before committing the final SPEC.md document.

Scoping phase workflow transitions involves loading PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md to establish context. The workflow then runs targeted interviews, scores ambiguity, and atomically writes SPEC.md to hand control to the next discussion phase.

Yes, you can auto-complete the spec-phase workflow by using the optional --auto flag. This bypasses manual Socratic questioning rounds and automatically processes the phase context to produce and commit the SPEC.md document.

The Socratic questioning process is limited to six interview rounds and requires an ambiguity score of 0.20 or lower to gate successfully. If ambiguity remains high after six rounds, the specification cannot be automatically committed without further manual clarification.

Yes, the spec-phase workflow supports plain-text output when invoked with the --text flag. This allows users to generate the clarified specification content in a non-markdown format while still utilizing the full Socratic questioning and ambiguity scoring mechanism.