interview-me

To clarify underspecified product management requests, this Skill conducts a one-question-at-a-time interview to extract true user intent, maintaining a confidence score until it reaches roughly 95% certainty about the underlying goal.

The best way to gather requirements for contextless requests is a one-question-at-a-time interview using a hypothesis-and-GUESS mechanism, which surfaces the who, why, and success criteria to prevent misaligned plans.

An intent interview reaches high confidence by asking clarifying questions sequentially and generating explicit GUESS prompts to accelerate alignment, concluding with a concise restatement of intent for downstream planning.

Yes, you can use one-question interviews to stimulate thinking for vague feature requests by triggering the interview mechanism, which actively surfaces true intent rather than what the user thinks they should want.

You should not use a one-question-at-a-time interview approach if the original request is already well-specified with clear who, why, and success criteria, as the mechanism is specifically designed for underspecified asks.