gsd-spec-phase

To generate a SPEC.md with structured requirements, you can execute the skill with the `--auto` flag to skip interactive questions and automatically write the document using recommended defaults for your software development workflow.

Ambiguity scoring evaluates phase deliverables across four weighted dimensions after each clarification round, providing quantitative analysis to ensure phase requirements are falsifiable and well-defined before moving to the next development phase.

You need to define phase deliverables when the what and why aspects of a phase are unclear, locking in critical details through ambiguity scoring to ensure structured requirements are validated before transitioning into the discuss-phase.

Yes, you can skip interactive prompts by executing the skill with the `--auto` flag, which writes the SPEC.md document directly using recommended defaults instead of requiring manual input for each clarification question.

Yes, ambiguity scoring works by applying quantitative analysis across four weighted dimensions to validate that your phase deliverables contain falsifiable requirements before they are locked into the SPEC.md document.

Using the `--auto` flag skips the interactive clarification process, meaning the generated SPEC.md relies entirely on recommended defaults without the iterative ambiguity scoring rounds that help reduce uncertainty in complex phase requirements.