Use AskUserQuestion to Eliminate Guesswork

What is AskUserQuestion?

When you give Claude Code a task, it usually just... does it. That's great when you're clear on what you want. But sometimes Claude makes assumptions you didn't intend, and you end up redoing work.

AskUserQuestion changes that. It's a built-in tool that makes Claude pause and ask clarifying questions before proceeding. Instead of guessing, Claude presents you with options, you pick, and then it continues with your actual preferences.

What it looks like

When Claude needs clarification, you'll see something like this in your terminal:

Claude has a question:

How should I handle duplicate entries?

  1. Keep the first occurrence
  2. Keep the last occurrence
  3. Keep the one with more data
  4. Remove all duplicates entirely

Type a number, or type your own answer:

You pick an option (or type something custom), and Claude continues with that direction locked in.

Why this matters for non-developers

If you're not a developer, you might not know the "right" answer to technical questions. That's actually fine — the point isn't to quiz you. It's to:

1. Surface decisions you didn't know existed — Claude might ask about edge cases you hadn't considered
2. Show you options — You learn what's possible while choosing
3. Prevent wasted work — Better to clarify upfront than redo later

When Claude uses it

Claude tends to ask questions when:

• There are multiple valid approaches and no obvious "right" one
• Your instructions are ambiguous
• A decision will significantly affect the output
• You're in Plan Mode (more on that below)

How to trigger it

You don't need to do anything special. Claude decides when to ask. But you can encourage it:

In your prompt:

Before you start, ask me any clarifying questions about how I want this done.

In your CLAUDE.md:

## Working style
- Ask clarifying questions before making assumptions
- When multiple approaches exist, present options and let me choose

Plan Mode + AskUserQuestion

This combo is powerful. When you use Plan Mode (/plan or start your prompt with "Plan:"), Claude builds a plan before executing. During planning, it's much more likely to ask questions.

> Plan: Create a weekly expense report from my bank CSV

Claude has questions:

1. What date range should the report cover?
   - Last 7 days
   - Current calendar week (Mon-Sun)
   - Custom range

2. How should I categorize expenses?
   - Use categories from the CSV
   - Auto-categorize based on merchant name
   - Ask me to define categories

...

You answer, Claude finalizes the plan, and then executes — with your decisions baked in.

Real example: Building a contact cleanup automation

Without AskUserQuestion, you might say:

Clean up my contacts.csv

Claude cleans it based on its assumptions. Maybe it removes entries you wanted to keep, or standardizes phone numbers in a format you don't use.

With AskUserQuestion encouraged, Claude might ask:

• "How should I handle entries with no email? Keep, remove, or flag?"
• "What phone format do you prefer: (555) 123-4567 or 555-123-4567?"
• "Should I merge duplicates or just flag them for review?"
• "The 'Notes' column has some empty cells. Delete the column, keep as-is, or fill with 'N/A'?"

You answer each one, and the output matches what you actually wanted.

Tips for getting good questions

Be a little vague on purpose — If you over-specify everything, Claude won't have anything to ask. Leave room for it to clarify.

Use Plan Mode for complex tasks — Planning naturally triggers more questions.

Add it to your CLAUDE.md — A simple "ask questions before assuming" instruction goes a long way.

Answer honestly — If you don't know, say so. "I'm not sure, what do you recommend?" is a valid answer. Claude will explain the tradeoffs and suggest one.

What you've learned

AskUserQuestion turns Claude from a tool that guesses into a collaborator that checks. Front-loading decisions means fewer surprises and less rework. Combined with Plan Mode, it's one of the best ways to get exactly what you want on the first try.