speckit-clarify

To clarify feature specs, the scan checks functional requirements, data models, UX, quality attributes, dependencies, edge cases, constraints, terminology, and acceptance criteria to detect missing details.

The guided clarification loop asks exactly one question at a time, up to five total, using multiple-choice options or tightly constrained short answers to minimize ambiguity before updating the spec.

Before clarifying specs, you must check prerequisites via a Powershell script and honor optional or middle extension hooks to ensure the project structure supports the interactive clarification process.

After clarifying specs, the updated feature specification with integrated clarifications serves as input for downstream product planning, task breakdown, and development workflow execution.

Complementary speckit tools manage the project structure, current spec file tracking, and feature spec creation, working in synergy to provide the baseline document for the ambiguity scan.

Alternative product planning tools offer manual review processes or general AI brainstorming to identify missing requirements, yielding less structured spec updates without interactive constrained Q&A.