gsd-spec-phase

Structured Socratic questioning reduces requirements ambiguity by running up to six interview rounds that uncover missing project phase details. It scores uncertainty across four weighted dimensions, ensuring requirements are clear enough to proceed before planning or implementation starts.

A falsifiable SPEC.md is a committed contract generated only when ambiguity scoring drops to 0.20 or below. You need it during phase-based planning to ensure later development phases rely on locked, testable specifications rather than vague assumptions.

To generate a locked project specification, load phase context files like PROJECT.md and ROADMAP.md, scout the current repository state, and run Socratic questioning. The system commits a falsifiable SPEC.md once the computed ambiguity score reaches the passing threshold.

Ambiguity scoring works with automated workflow pipelines by supporting both interactive and auto modes. It quantifies requirements uncertainty across four weighted dimensions after each interview round, allowing automated systems to gate specification generation without manual intervention.

Socratic questioning requires loading phase context files including PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md. These files provide the necessary project baseline and current codebase state before the interview loop and ambiguity scoring begin.