clarify

To resolve ambiguities in an existing feature spec, you can use a guided clarification flow that identifies gaps across functional scope, data models, and edge cases, then asks structured questions to update the document with validated answers.

The best way to clarify requirements is by applying a taxonomy of ambiguities to prioritize up to five high-impact questions, presenting them one at a time to ensure focused responses before persisting the answers to the spec.

Yes, you can use an interactive question flow to update a spec.md file directly, as accepted answers are integrated back into the document under a dedicated Clarifications section while preserving the original structure.

Yes, the clarification process covers non-functional requirements and integrations by applying a taxonomy that also includes UX flow, data models, functional scope, edge cases, and terminology to ensure comprehensive spec validation.

You should refine a spec when an existing document like spec.md already exists and needs ambiguities resolved, whereas creating a new spec from scratch requires a different specification tool.

During the spec refinement flow, up to five clarifying questions are prioritized based on impact and feasibility, and are presented one at a time to maintain an interactive and manageable update process.