Ask most AI tools to turn a pile of notes into a document. They hand you three fat paragraphs before you have said what you actually need. That is exactly the frustration u/Big_Currency_1805 ran into on r/PromptEngineering, and the fix this Redditor found flips the usual order on its head.
The problem was familiar to anyone who has fed rough notes into a document generator. It inflates everything into padded prose with a generic structure that never matches your intent. You end up rewriting the whole thing anyway. So the original poster stopped asking the model to write first and started forcing it to plan first.
Key Idea: Structure Before Prose
Most prompts jump straight into writing. This one refuses. It reads your notes and guesses what kind of document you are building. Then it proposes a section outline, with a one-line purpose for each part. Only once that skeleton is confirmed does it start drafting. Nothing gets written until the shape is right.
That single change, separating structure from prose, is why this approach saves so much rewriting. The model cannot invent a wrong framing and bury it under 800 words before you notice.
🧭 Old Way vs New Way
Here is the contrast, side by side.
The old way, step by step:
- Dump your notes in.
- Get inflated paragraphs back immediately.
- Discover the structure does not match what you meant.
- Rewrite the entire draft from scratch.
The new way, step by step:
- The model states its guess about the document type.
- It shows you the outline first.
- It flags anything contradictory or too thin to support a section.
- It asks up to three questions, then waits for your answers.
- Only then does it write the full document, once.
The old approach front-loads the writing and back-loads the fixing. The new approach reverses that. You catch the wrong framing in the outline stage, before a single paragraph exists. That is a lot cheaper than catching it after 800 words.
The Four-Step Prompt
Here is the prompt exactly as the original poster wrote it, ready to copy:
You are helping me turn a rough brain-dump into a finished document.
Input: a pile of unordered notes (below).
Step 1. Read everything and infer what document this is meant to be (proposal, spec, memo, guide). State your guess in one line.
Step 2. Propose a section outline. For each section give a one-line purpose. Do NOT write prose yet.
Step 3. Flag anything in my notes that is contradictory, missing, or too thin to support a section. Ask me at most 3 questions.
Step 4. Wait for my answers, then write the full document in plain language. No filler sentences, no throat-clearing intros.
Notes: [paste your brain-dump]
A few things make this work. Step 1 forces the model to commit to a genre before it commits to content. That stops it from drifting between “memo” and “proposal” halfway through. Step 2 bans prose entirely, so you are reviewing a skeleton, not a half-finished draft you have to mentally discard. Step 3 is the real unlock: the “at most 3 questions” cap keeps the model honest about what it truly cannot infer. Without that cap, the model either asks nothing and guesses wrong, or buries you in a checklist. Three questions forces real prioritization instead of laziness or overkill.
Where This Helps Most
This structure-first approach earns its keep on anything with real stakes riding on the framing:
- 📋 Project proposals, where the wrong section order buries your ask on page three.
- 🗂️ Technical specs, where a missing section means a rebuild later.
- 📄 Internal memos, where the “document type” itself is often unclear from the notes alone.
Make It Sharper
A few commenters pushed the idea further, and their tweaks are worth stealing.
One reader argued the model should be more adversarial toward both you and itself, not just polite about gaps. If your notes are thin, you want the model calling that out directly, not softening it.
Another suggested turning Step 3 into an interactive questionnaire inside tools like Claude, instead of a flat list of questions. That makes the back-and-forth feel less like filling out a form.
A third pointed out the model can be too polite when flagging contradictions. Their fix: add a line telling it to be blunt about what does not add up.
None of these break the core structure. They just sharpen the parts that were already doing the work.
Try running your next messy brain-dump through this before you touch a document generator the usual way. Read the full thread for more of the back-and-forth on the question-limiting step. That is the part readers keep coming back to.
Frequently Asked Questions
Q: Should you limit questions to 3, or ask for more?
The original prompt caps questions at 3 to keep exchanges tight. However, commenters suggest requiring at least 3 per section instead, this catches more gaps but takes longer. Start with max-3 overall, but if you find yourself rewriting because details were missed, switch to demanding per-section minimums.
Q: Should the AI adopt a specific expert persona?
Yes. Instead of generic instructions, assign the AI a role like “You are a senior [domain] expert reviewing these notes.” This grounds the AI in domain-specific knowledge, so it flags gaps and contradictions you’d otherwise miss.
Q: How should the AI handle contradictions in your notes?
The AI tends to politely reconcile contradictions rather than flag them bluntly. Add a line like “Be honest about gaps and contradictions, don’t try to smooth things over.” This keeps the AI from inventing diplomatic explanations for what’s actually missing or inconsistent.
Q: Is it worth having the AI review its own draft?
Yes. After the outline and questions pass your review, have the AI review its first draft antagonistically, flagging weak sections and asking itself clarifying questions. This extra pass catches inconsistencies before you spend time on manual edits.
Here’s a prompt that turns a messy brain-dump into a clean document instead of the usual document generator wall of text
by u/Big_Currency_1805 in PromptEngineering