speckit-clarify

To resolve ambiguity in a feature specification, you can use a clarification process that analyzes your spec and asks up to 5 targeted questions to address underspecified areas. This directly updates and refines the feature specification quality.

You need to refine a feature spec before planning when the specification contains underspecified areas. Asking targeted clarification questions helps reduce ambiguity and ensures all requirements are clearly defined before moving into the planning phase.

Yes, spec-kit supports automatic clarification through targeted scripts that ask up to 5 questions to resolve ambiguity. It utilizes YAML parsing and Markdown file manipulation to record clarifications directly in the spec file.

You can update a Markdown feature spec by running a clarification skill in your project directory. The skill manipulates the Markdown files and records your clarification answers directly within the existing feature specification document.

Yes, you need a spec-kit project structure with a .specify/ directory to clarify feature specifications. The clarification process relies on this specific project layout to parse YAML and manipulate Markdown spec files correctly.

The limit for feature specification refinement is up to 5 highly targeted clarification questions. This constraint ensures that only the most critical underspecified areas are addressed, reducing ambiguity without overwhelming the user.