speckit-clarify

To reduce ambiguity in a feature spec, an interactive clarification process scans for underspecified areas across functional, UX, and edge case dimensions, then asks targeted questions and writes the accepted answers directly back into the spec.

A spec clarification process checks for gaps in functional requirements, data models, UX, non-functional constraints, integrations, edge cases, terminology, and completion criteria to ensure comprehensive coverage before downstream planning.

You interactively clarify requirements discovery gaps by running an automated scan that selects the highest-impact uncertainties and asks exactly one targeted question at a time, using constrained answer formats to collect precise decisions.

Yes, spec clarification handles incremental updates by ensuring a Clarifications section exists in the spec file, recording each accepted answer, applying minimal targeted edits, and saving the file after every single interaction.

Yes, there are strict limits to spec clarification: the process asks a maximum of five targeted questions, selecting only the highest-impact and most uncertain gaps to resolve, preventing excessive questioning during requirements discovery.

To run an ambiguity scan on a spec-kit structure, you need a current feature spec requiring reduced ambiguity and must pass hook-aware pre-checks and prerequisite verification via a check-prerequisites script before the interactive questioning starts.