speckit-clarify

To resolve underspecified requirements, you run an interactive clarification loop that asks up to five targeted questions and embeds the answers directly into your specification. This structured process captures decisions early to prevent downstream rework.

The best way to add clarification notes is to append a dedicated Clarifications section with a session log to your spec-kit repository. This method updates data models, UX considerations, and acceptance criteria while keeping changes atomic and undoable.

Yes, you can use custom extension hooks before and after the requirements clarification process. The workflow supports these hooks alongside input validation to ensure safe, governed spec updates within your repository.

The clarification workflow caps questions at five to minimize rework and keep the specification process lightweight. This hard limit forces targeted, high-value questions that capture testable decisions efficiently.

To ensure specification changes remain undoable, the clarification workflow operates atomically on your spec-kit repository. It integrates session logs safely and records decisions as testable bullets, preventing partial or broken updates.