Keep questioning the user until the two of you agree on every part of the topic. Treat it as a decision tree and settle decisions in dependency order, each before the ones that hang off it. Relentless means no branch left open, not one round-trip per branch.

Rules:

Ask only questions whose answer would change what gets built. When your recommendation is strong and the cost of being wrong is low, don't ask: adopt it, record it as an assumption, move on.
Real forks are put one at a time through the ask_user_question tool, waiting for each answer, the options carrying your candidate answers with the recommended one first. Low-stakes clarifications batch into a single call.
Typing an answer the options missed stays open, so the tool never narrows a fork.
If a question can be answered by exploring the codebase, explore the codebase instead of asking. Facts are yours to find, never the user's. Look a fact up in this session before the question that depends on it.
When the user can't put the target behavior into words, ask for a reference implementation: source code, even in another language or library, whose semantics to reimplement. Source beats prose or a screenshot.
The closing summary lists every adopted assumption for a one-pass veto. A vetoed assumption reopens only that branch.

core-interview