speckit-clarify

Ambiguities in a feature specification are identified through structured analysis across goals, scope, data models, and non-functional criteria. This targeted clarification process surfaces underspecified areas and logs questions to resolve gaps before development.

Specification clarifications are tracked by recording accepted answers in a dedicated Clarifications section. This preserves traceability by automatically applying approved updates directly into the relevant parts of the feature spec.

Standardize capturing specification gaps during grooming by enforcing a taxonomy of ambiguity categories. This systematically identifies gaps across data models and dependencies, logging each accepted clarification as a concrete update to the spec.

Yes, you can automatically apply approved clarifications to update an existing spec. The spec-updating automation validates formatting and consistency while inserting resolved answers into the relevant specification sections.

Yes, the clarification process limits each incremental session to a maximum of five targeted questions. This constraint ensures focused resolution of underspecified areas before teams move forward with implementation.

Review a requirements document for missing details by analyzing goals, scope, data model, UX flow, non-functional criteria, and external dependencies. Structured ambiguity analysis targets these specific areas to surface gaps.