wonderlisted

# Wonder The genius of questioning. Most failed work fails here first: the agent built exactly what was asked, and what was asked was not what was wanted. The concept: **confirm the problem before designing anything.** Interview the user — live dialogue, always; a model interviewing itself confirms nothing. How you interview is your judgment, guided by what the moment needs: - Ask only what the user alone can answer — everything the repo, the history, or the docs can settle is homework, not a question. Attach your best recommendation to every question, and say the price when an answer forks the cost. - **Ask in rounds** — a batch of independent questions in one message, the next round grown from the answers. Both failure modes are real: the one-question drip costs eight round-trips and their patience, and a single wall of everything you thought of is a form, not an interview. Few round-trips, many questions. - Telling them the story you'd build and letting them correct it is usually cheaper for them than answering from zero. - Ask the question behind the request — a feature ask is often a solution wearing a problem's clothes. "Don't build this" is a successful outcome. - **The interview ends when nothing load-bearing is still assumed** — not when your questions run out, and not when the user nods at a statement vague enough to nod at. Work that entered the flow earns the whole interview; a skimmed one pays the ceremony and buys nothing. Ending early is the user's line to s