speckit-clarify

To identify ambiguities in a feature specification, use a structured clarification workflow that detects underspecified areas across functional requirements, data models, and UX flows. It generates targeted questions to resolve gaps and records answers directly into the spec.

The best way to add clarifications to a spec while keeping it traceable is to record accepted answers under a dedicated Clarifications section. This ensures decisions are documented, testable, and aligned with planning within the specification workflow.

You can generate targeted questions for underspecified functional requirements by running a two-stage clarification process against your specification. This interactive questioning loop produces up to five questions to collect missing details and apply them back into the document.

Yes, the spec clarification process supports an interactive questioning loop that collects answers and applies them automatically. It updates the specification document to reflect decisions, ensuring changes are traceable and testable within the workflow.

Yes, you can review specification clarifications after they are recorded into the document. Accepted answers are stored under a specific Clarifications section, allowing you to review decisions later and maintain alignment with planning.