speckit-clarify

To identify ambiguities in feature specifications, apply structured scanning across functional scope, domain model, interaction flows, non-functional constraints, and acceptance criteria. This process surfaces underspecified requirements at the pre-planning stage to ensure decisions are captured.

The best way to clarify underspecified requirements is running a structured clarification workflow that records clarifications with traceable provenance in a dedicated session log. This integrates directly with the spec-kit workflow to minimize downstream rework.

Yes, the speckit-clarify workflow requires an active feature with a .specify/ directory. It integrates into existing spec-kit workflows by operating within this established project structure to apply pre-planning guardrails.

Structured ambiguity scanning works by systematically questioning underspecified areas across functional scope, domain model, interaction flows, and acceptance criteria. It uses coverage-based questioning to ensure all clarification decisions are captured with traceable provenance.

Requirement ambiguity causes downstream planning rework because underspecified features lead to misinterpretation during implementation. Applying pre-planning guardrails to resolve these ambiguities early ensures decisions are captured and rework is minimized.

Yes, you can use this clarification workflow for non-functional constraints and acceptance criteria. The structured ambiguity scanning explicitly covers these areas to surface and resolve underspecified requirements before planning begins.