speckit-clarify

You can resolve ambiguities in a feature specification by using a guided tool to generate up to 5 targeted clarifying questions. It asks questions one at a time and applies accepted answers directly back into the spec file.

Tracking requirement changes to a spec is effectively done by committing each accepted clarifying answer as a separate git commit. This creates a clear audit trail directly within your version control history for every updated requirement.

Finding missing non-functional criteria in project requirements is done by running a guided ambiguity detection session. It scans your spec for gaps across functional scope, data models, UX flows, and external dependencies to surface underspecified areas.

Yes, a .specify project structure is required to clarify feature specs with this tool. The Skill operates within this specific directory structure to ensure consistency between your planning phase and execution phase.

Underspecified areas in a spec that can be clarified include core goals, data models, UX flows, non-functional criteria, and external dependencies. The detection covers all these dimensions to prevent misaligned implementations.