gsd-spec-phase

This Skill clarifies ambiguous project phase requirements by running a Socratic interview loop with quantitative ambiguity scoring, loading existing context like PROJECT.md and REQUIREMENTS.md, and then writing a falsifiable SPEC.md gated by ambiguity thresholds.

Socratic ambiguity scoring is a structured interview mechanism that evaluates requirements vagueness across weighted dimensions through up to six rounds, enforcing minimum dimension gates before allowing a falsifiable SPEC.md to be written for a project phase.

You can generate and commit a gated SPEC.md automatically by running the spec-phase command with the target phase name, which triggers codebase scouting, context loading, and the Socratic interview loop to produce the final specification document.

Yes, the process requires loading existing project context from PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md to scout the codebase and inform the Socratic question rounds before writing the phase SPEC.

You should avoid automated SPEC generation when your project phase lacks fundamental context files like PROJECT.md or ROADMAP.md, as the Socratic interview relies on scouting existing codebase state to evaluate ambiguity and enforce dimension gates.