speckit-clarify

You can identify underspecified areas in a feature spec by running a focused clarify workflow that generates up to five targeted questions to resolve early ambiguity before planning begins.

A spec clarification workflow reduces ambiguity by asking up to five highly targeted questions about an active feature specification, then encoding the accepted answers directly back into the spec document.

Yes, the spec clarification process is compatible with spec-kit projects that use a .specify/ directory, loading and modifying the spec document to append accepted Q/A entries into a Clarifications section.

The best way to update acceptance criteria after resolving ambiguities is to use a clarify workflow that encodes accepted answers directly into the spec, persisting changes to disk with atomic writes.

You should clarify requirements before planning to minimize downstream rework, ensuring that all early ambiguities are resolved and encoded into decisions and acceptance criteria prior to execution.

Yes, you can manage an in-session Clarifications section within the active spec document, appending Q/A entries after acceptance and persisting all changes to disk using atomic writes.