speckit-clarify

To identify underspecified areas in a feature specification, load the active FEATURE_SPEC to detect ambiguity and missing decisions, then generate up to five targeted clarification questions for stakeholders to resolve uncertainty.

You generate clarification questions for vague requirements by running the spec-kit clarification flow, which analyzes the FEATURE_SPEC and produces up to five prioritized questions answerable as short phrases or multiple-choice options.

The best way to resolve missing acceptance criteria is to use a spec clarification process that generates targeted questions, ensuring architecture decisions align with stakeholder intent before downstream planning or implementation begins.

Yes, you need a .specify directory containing a FEATURE_SPEC file. The workflow requires running the check-prerequisites.ps1 script to validate the repository environment before generating clarification questions.

Spec clarification encodes accepted answers back into the feature spec by performing atomic spec updates. This incrementally writes validated clarifications directly into the FEATURE_SPEC file to maintain consistency.