speckit-clarify

To identify gaps in a feature specification, scan the document for ambiguity across functional scope, data models, user interactions, non-functional criteria, and edge cases using targeted clarification questions.

The best way to clarify ambiguous requirements is through an interactive session that prompts up to five targeted clarification questions, then encodes the validated answers directly back into the specification document.

Document specification clarifications by maintaining a dedicated Clarifications section within the spec that logs all decisions, saving changes to the document incrementally after each accepted answer.

You can resolve multiple ambiguities in a single session, but the workflow enforces a strict limit of up to five targeted clarification questions per session to maintain focus and prevent scope creep.

Check functional scope, data models, user interactions, non-functional criteria, and edge cases for missing requirements to ensure comprehensive feature specification coverage before engineering begins.

The specification clarification workflow updates the document automatically by iteratively applying validated clarifications and saving changes to the spec after each accepted answer during the session.