gsd-spec-phase

Automating phase specification involves running a structured Socratic interview loop to refine requirements, which then generates a SPEC.md document with falsifiable deliverables and ambiguity scoring for your project phase.

Ambiguity scoring in project management specifications evaluates requirements across weighted dimensions during an interview loop, ensuring deliverables are clearly defined and falsifiable before moving to the discussion phase.

To conduct a Socratic interview loop for phase deliverables, execute the specification workflow with your phase context files, allowing the system to ask structured questions and score ambiguity until requirements are locked.

Yes, phase context files and workflow execution are required to run automated specification generation, as they provide the necessary inputs for the Socratic questioning loop and ambiguity scoring process.

Use an automated specification document when you need to lock the 'what and why' of project phases early, ensuring falsifiable requirements and reducing ambiguity before entering the discussion phase.

Yes, you can specify a particular project phase number for automated SPEC.md generation by passing the phase number as an argument when executing the specification workflow command.