speckit-clarify

Feature specification gaps are identified by prompting up to five targeted clarification questions, then encoding the accepted answers directly back into the spec under a new Clarifications section.

The best way to log clarifications is to append answers into a new Clarifications section with a daily session subheading and bullet log, writing to the spec after every accepted answer to ensure traceability.

Yes, you can use an AI-assisted workflow that enforces a single-question-at-a-time loop, limiting the session to five questions and validating changes before saving the updates to your FEATURE_SPEC.

A targeted clarification loop improves requirements traceability by appending accepted answers to the specification with a daily session subheading and bullet log, creating a clear audit trail of changes.

The limitation is that the clarification loop is capped at five questions per session, meaning highly complex or deeply underspecified features may require multiple separate sessions to fully resolve all requirements gaps.