clarification-phase

To resolve ambiguities in project specifications, you can execute a structured clarification phase to identify unclear requirements and ask stakeholders prioritized questions. This ensures all critical scope and security details are disambiguated before planning begins.

The best way to ask users for clarification is to formulate structured, prioritized questions with concrete options and impacts. Presenting up to three targeted questions at a time ensures high-priority requirements are effectively disambiguated without overwhelming the user.

To handle deferred assumptions during requirements clarification, document them explicitly after asking the user questions. The clarification process integrates user responses back into the specification while logging any assumptions that cannot be immediately resolved.

Yes, you can use this clarification approach to disambiguate scope, user experience, and security questions for new features. It identifies critical and high-priority items in your specification document and ensures they are answered by stakeholders before development starts.

You need to run a clarification phase after drafting a specification document but before starting the planning stage. It resolves any [NEEDS CLARIFICATION] markers in your spec file, preventing costly rework during development later in the project lifecycle.