speckit-clarify

To resolve ambiguity in feature specifications, you can use a clarification tool that scans your spec and asks up to 5 targeted questions to identify and fill underspecified areas. This ensures all aspects are clearly defined before planning.

The best way to clarify underspecified areas is through structured ambiguity scanning that generates targeted questions. Answers are then encoded directly back into the feature specification file, improving overall spec quality.

To integrate clarification answers into your spec-kit specification, the Skill automatically encodes your responses directly back into the spec file. This updates the document within your existing project structure.

Yes, you need a spec-kit project structure with a .specify/ directory to use this specification clarification tool. The Skill relies on this specific environment to scan and update feature specifications.

You should run specification clarification during feature development when you have an initial spec draft. Use it to ensure all aspects are clearly defined and ambiguity is resolved before proceeding to the planning phase.

Yes, you can target specific areas to clarify in your feature specification. The command accepts optional parameters to focus the ambiguity resolution and coverage scanning on particular sections of your spec.