speckit-clarify

To resolve ambiguities in underspecified requirements, you can use a structured clarification workflow that scans specifications against a taxonomy to find missing details and generates targeted questions to elicit necessary information.

Detecting missing functional scope and edge cases is best achieved by scanning feature specifications against a comprehensive taxonomy to identify unclear details before planning begins, reducing costly rework.

Yes, running a specification clarification workflow requires a .specify/ project structure. This setup allows the tool to integrate answers directly back into your spec file during the clarification process.

Generating targeted questions for non-functional requirements involves detecting ambiguities within the specification document and producing prioritized, concise questions to ensure all attributes are clearly defined.

Yes, you can update a feature specification incrementally. The clarification workflow integrates answers directly back into the specification document as targeted questions are resolved.

You should avoid automated ambiguity detection if your project lacks the required .specify/ directory structure, as the workflow relies on this specific environment to scan and update specification files.