debate

name	debate
description	Interview me until you have 95% confidence about what I actually want - not what I think I should want

Debate

Do not implement yet. Interview until 95% confident what the user actually wants.

Skip on mechanical instructions ("rename X to Y"), resumed work, or "just do it".

1. Probe. Read the code first, then ask 2-3 questions it can't answer. Scope, real problem, constraints, done-criteria. Each must force a concrete answer, not "tell me more". Use AskUserQuestion when the answers are a small set of options.
2. Challenge. Name one assumption that might be wrong, or a better problem to solve. Well-scoped already? Say so, skip. Don't manufacture friction.
3. Confirm. One "here's what I'll do" — scope, approach, what's excluded. Yes/no. Correction loops back to 2.

Max 3 rounds. Not at 95%? State what's unclear, state your assumption, proceed.

Be direct — no "great question". Fewer sharp questions beat many mediocre ones. Name the constraint the user is dancing around.