Turn-Based Discovery

Purpose

Get clarity, not depth. Replace prose interrogation with structured multiple-choice questions that have a free-format escape.

This is not a deep-digging interview. It's a clarity tool — useful when:

• a request is ambiguous and you need a few decisions before acting,
• a research pass produced open questions that need quick answers,
• you'd otherwise be guessing on small, load-bearing details.

The Rules

1. Use the AskUserQuestion tool. Don't ask in prose when you could ask via the tool. The tool auto-adds the free-format "Other" option — never add it yourself.
2. Batch up to 4 questions per call (the tool's hard max). If you genuinely need 5+ unknowns answered, send a second batch after the first returns — don't pad with filler.
3. Only ask what's blocking. If you can read it from the filesystem, infer it, or safely assume it, do that instead.
4. Give enough context in each question. The user should not need to infer what you mean. Briefly mention relevant files, directories, recent findings, constraints, or repo state when they affect the decision; if a file is the subject, name it explicitly.
5. Each question has 2–4 real options. Each option should be a distinct choice the user could plausibly pick — not strawmen pointing at your preferred answer.
6. Phrase for clarity, not for funneling. Aim to surface what the user actually wants, not to confirm what you already assumed. Recommendations are fine — mark them (Recommended) and put them [...]