speckit-clarify

To clarify ambiguity in a feature specification, you interactively answer up to five targeted questions about missing decisions. The tool scans for gaps across functional, data model, and edge case areas, then writes your answers directly back into the spec.

Detecting missing requirements in a spec-kit project involves scanning the active feature spec for underspecified areas across functional, data model, UX, and terminology domains. The tool identifies these gaps and prompts you for targeted clarification.

Yes, you can use interactive questioning to update a feature spec incrementally. The tool asks a single question at a time, applies each accepted answer immediately under a Clarifications section, and performs an atomic save after every response.

Yes, the spec clarification process supports optional pre and post extension hooks. It executes before_clarify and after_clarify hook commands when configured, allowing integration into wider spec-kit workflows without interpreting hook conditions.

Limitations of automated ambiguity detection include a strict maximum quota of five clarification questions per session. Additionally, free-form answers must be five words or less, and the tool aborts if the prerequisite feature directory or JSON payload cannot be located.

Yes, you need a specific directory structure for spec clarification. A pre-flight environment check requires locating the active feature spec within the .specify structure, and the process aborts immediately if the feature directory or spec file cannot be parsed.