Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Story

Reddit user suggests asking Claude for clarification before drafting

AI summary

A Reddit user proposes giving Claude a rough task and asking it to request any information needed before beginning. The author says Claude typically asks three to five questions about audience, tone, constraints, and inclusions, but acknowledges that this adds a back-and-forth step and is unsuitable for one-shot answers.

In-depth insight

The technique offers users a simple way to expose gaps in a brief before drafting, particularly for writing, long-document summaries, and multi-part planning.

Most people try to write the perfect prompt on the first try. Pack in every detail, every constraint, every edge case.

There's a simpler approach: give Claude the rough task, then add this line at the end. "Before you start, ask me any questions you need answered to do this well."

Claude usually comes back with 3-5 questions covering things you didn't think to mention: - Who's the audience? - What tone are you going for? - Are there constraints I should know about? - Should anything specific be included or left out?

After you answer those, the first draft is much closer to what you actually wanted.

Why this works: you don't know what you don't know. When you write a detailed prompt, you include the details that seem important to you. But Claude can spot gaps in your brief that you can't see because you're too close to it. It's like the difference between writing a design doc alone vs having someone ask you clarifying questions first.

This is especially useful for: - Writing tasks where tone and audience matter - Summarizing long documents when you're not sure what angle you need - Planning anything with multiple moving parts

The trade-off: it adds a back-and-forth step, so it's not ideal when you need a one-shot answer. For anything important though, the extra Q&A round usually saves you from doing several revisions after.

You can also tighten it up. Instead of a general "ask me any questions," try "ask me up to 5 questions about audience, format, and constraints before you begin." That keeps the questions focused on things that actually shape the output.

What types of tasks have you found this works best for? Anyone run into cases where it backfired or made things worse?

#Claude

Original · 1 min readRead the original
Group chat

No comments yet. Start the conversation.