speckit-clarify

To resolve ambiguity in a feature specification, you can generate targeted clarification questions that expose underspecified areas. This process detects gaps in your spec and asks up to 5 focused questions to fill them before planning begins.

You need to clarify underspecified areas in technical specifications before moving to the planning phase of feature development. Resolving these gaps early through targeted questions prevents misalignment and ensures the technical specification is complete enough to guide implementation.

Yes, feature specification clarification is designed specifically for spec-kit projects. It requires a .specify/ directory and executes pre and post clarification checks by integrating with hooks defined in the spec-kit extensions.yml file.

To start clarifying your feature spec, run the /speckit-clarify command within your spec-kit project environment. This initiates the script execution that analyzes your specification and generates the targeted clarification questions.

A limitation of specification clarification is the strict dependency on spec-kit and its .specify/ directory structure. Projects not structured for spec-kit cannot utilize the pre and post clarification check scripts or the extensions.yml hook integrations.

No, the specification clarification process generates a maximum of 5 targeted questions to resolve ambiguity. This limit ensures the clarification remains focused on the most critical underspecified areas within the feature specification.