speckit.clarify

To resolve ambiguities in a feature specification, this Skill asks up to five targeted clarification questions based on impact and uncertainty, then encodes your answers directly back into the spec file to improve overall spec quality.

Identifying underspecified areas in software requirements is handled through structured ambiguity detection, which automatically finds gaps in your feature spec and prioritizes questions to resolve the highest impact uncertainties first.

Yes, specification clarification requires a spec file generated by the speckit.specify dependency, as it operates within the scope of feature specification reviews and uses that output to identify ambiguities.

Yes, you can update your existing feature spec automatically because the Skill encodes your answers from the targeted clarification questions directly back into the original spec file.

You will be asked up to five highly targeted clarification questions when reviewing a feature spec, specifically prioritized by their impact and uncertainty to resolve ambiguities efficiently without overwhelming the review process.

You should use targeted questions for specification management when reviewing a feature spec to ensure all requirements are clear and complete, specifically before proceeding to the planning phase of your software design workflow.