speckit-clarify

Spec clarification works by scanning an active feature spec for underspecified requirements across architecture, UX, and data modeling. It interactively asks up to five targeted questions to resolve ambiguity and logs decisions back into the spec.

You resolve non-functional requirements and edge cases by interactively answering targeted multiple-choice or short-answer questions. The tool scans your spec for these specific gaps and asks up to five questions to quickly converge on necessary architecture and testing decisions.

Yes, spec clarification requires an active spec-kit project with an existing feature directory and spec file. The tool runs prerequisite checks on this environment to identify ambiguities and then incrementally updates your spec file with the accepted answers.

The best way to document architecture decisions and coverage gaps is to run an interactive Q&A session on your feature spec. It immediately writes accepted answers back into the appropriate spec sections, creating a structured daily Clarifications log for tracking.

Yes, a key limitation is that the spec hardening process asks no more than five high-impact questions per session. This constraint ensures you quickly converge on critical decisions for testability and architecture without stalling the planning phase.