interview-me

Intent validation builds shared understanding of outcomes and constraints before downstream work. It tracks confidence levels and requires explicit confirmation to ensure requirements are fully captured before planning or implementation.

A discovery interview for underspecified feature ideas guides users through one-question iterative questioning with explicit hypotheses. This uncovers hidden requirements and validates actual product intent before specification.

You need to extract user intent before planning when receiving underspecified product requests. If a user asks to build a dashboard without explaining the audience, intent extraction prevents wasted implementation effort.

Yes, you can use hypothesis-driven questioning to prevent building the wrong product. This approach applies iterative questions to uncover actual goals and success criteria before coding or specification work begins.

Intent discovery works effectively for underspecified product requests by applying iterative questions. It clarifies missing goals, constraints, and non-goals, ensuring explicit intent confirmation before handing work to downstream skills.