speckit-clarify

To clarify ambiguous feature specifications, you can scan the spec document to detect missing decisions and ask up to five targeted clarification questions, writing accepted answers directly back into the appropriate spec sections to reduce downstream rework.

Ambiguity detection in requirements identifies underspecified areas in UX flows, data models, and non-functional constraints. Resolving these ambiguities ensures acceptance criteria are testable and aligned before feature planning begins.

You resolve missing edge cases and non-functional constraints by running a structured ambiguity scan that prompts up to five high-impact clarification questions, incrementally updating the spec with constrained answer formats after each response.

Yes, spec clarification works with spec-kit workflows by executing a prerequisite check to locate your existing FEATURE_DIR and FEATURE_SPEC, then applying an ambiguity scan and writing validated incremental edits back into those files.

Automated spec clarification is limited to asking up to five targeted questions per run and requires constrained multiple-choice or short answers, meaning it cannot resolve open-ended design debates or fully replace collaborative requirement gathering sessions.