speckit-clarify

To clarify ambiguous requirements in a feature spec, load your active spec to start an interactive session that asks up to five targeted questions across functional, domain, interaction, non-functional, and edge-case categories. Answers are appended directly into a Clarifications section.

An ambiguity and coverage scan for feature specifications is a structured assessment that identifies underspecified areas across functional, domain, interaction, non-functional, and edge-case categories. It generates targeted clarification questions to resolve gaps and update the spec automatically.

To find missing edge cases in product requirements, run a structured ambiguity scan on your feature spec. The tool evaluates coverage across multiple categories and prompts up to five focused questions to surface and resolve underspecified edge-case scenarios.

Spec clarification works with your existing feature specs by loading the active document directly. There are no external dependencies required; the tool scans the loaded spec content and appends resolved answers under a new top-level Clarifications section.

The best way to document requirement clarifications without losing traceability is to append answers to a dedicated Clarifications section in the spec while applying them to relevant sections. The tool also maintains session-scoped notes for full traceability of each accepted answer.

Yes, you can limit clarification questions during a spec review because the interactive questioning loop is constrained to a maximum of five highly targeted questions. This ensures the ambiguity scan remains focused and actionable without overwhelming the user.