speckit-clarify

To identify ambiguities in a feature specification, you can generate up to five targeted clarification questions addressing functional, data, UX, non-functional, and integration areas. This process highlights underspecified areas needing further detail.

The best way to update a spec with clarification answers is to encode the accepted responses directly back into the specification. This adds a 'Clarifications' session to the SPEC, ensuring traceability and reducing future rework.

To resolve underspecified requirements before development, generate high-impact clarification questions targeting ambiguous spec areas. Encoding the accepted answers back into the SPEC ensures terminology consistency and testable acceptance criteria.

Yes, you can integrate spec clarification workflows with speckit extensions. The workflow leverages an extension mechanism around .specify to manage pre- and post-clarification hooks, updating the SPEC systematically after each accepted answer.

Yes, a limitation exists: you can generate a maximum of five targeted clarification questions per feature specification. This constraint ensures high-impact questioning across functional, data, UX, non-functional, and integration ambiguities.