Six Ways to Rewrite a Weak Prompt (With Before-and-After Examples)
Short answer: A weak prompt usually fails for one of six specific reasons — it's ambiguous, it's missing context, it asks for too much at once, it doesn't specify a perspective, it's cluttered with irrelevant detail, or it just needs a general pass. Six matching techniques — Clarify, Elaborate, Step-by-step, Expert, Concise, and Combine — address each failure mode. Below is a before-and-after for each.
"Write me a blog post about productivity" and "Write a 600-word blog post for busy freelancers, arguing that most productivity advice fails because it optimizes for the wrong constraint, in a direct and slightly contrarian tone" will not get you the same essay. Same model, same request in spirit, wildly different output — because the second version removed every decision the model would otherwise have had to guess at. Rewriting a prompt is mostly the work of finding which guesses you're forcing the model to make, and closing them off one at a time.
These six techniques cover the main ways prompts go wrong.
1 · Clarify — Remove ambiguity, sharpen intent
The most common failure mode isn't a bad idea, it's an underspecified one — a request that could reasonably be answered five different ways, so the model picks one and you get something adjacent to what you wanted rather than the thing you actually meant.
| Before | After |
|---|---|
| Can you help me with my resume? | Review my resume for a mid-level product manager role. Flag anything vague or generic, and point out where the bullet points describe responsibilities instead of measurable outcomes. |
The rewrite doesn't add much new information; it simply narrows the five different tasks "help me with my resume" could have meant — proofreading, formatting, rewriting from scratch, tailoring to a job post — down to exactly one.
2 · Elaborate — Add context, constraints, and audience
Some prompts are clear about the task but silent on everything surrounding it — who it's for, what's already been tried, what a good answer would need to account for. The model fills those gaps with plausible defaults that may have nothing to do with your actual situation.
| Before | After |
|---|---|
| How do I reduce churn? | We're a B2B SaaS product with $80/month average contract value, and churn is concentrated in the first 30 days after signup, not later. What are the most likely causes for early-specific churn, and how would you diagnose which one applies to us? |
The first version could get a generic churn-reduction listicle. The second forces an answer that engages with the actual shape of the problem instead of the general category it belongs to.
3 · Step-by-step — Decompose into structured actions
Compound requests — several tasks stacked into one sentence — tend to get a shallow pass at everything rather than a real answer to any one part. Breaking the request into an explicit sequence usually gets more useful depth on each piece.
| Before | After |
|---|---|
| Help me plan a product launch. | Help me plan a product launch in four stages: (1) list the channels worth considering for a $5K budget, (2) draft a two-week content calendar for the top three, (3) identify what could go wrong at launch and a mitigation for each, (4) define what "successful launch" means in measurable terms. |
Same underlying goal, but the model now has a structure to fill in instead of an open field to wander across, which usually leads to deeper, more useful answers for each part — four distinct, checkable outputs instead of one paragraph that gestures at all of them.
4 · Expert — Reframe from a specific perspective
Without a stated perspective, the model defaults to a generalist tone that hedges across audiences. Naming the vantage point you actually want narrows both the content and the tone of the answer.
| Before | After |
|---|---|
| Is this contract clause a problem? | As a contracts lawyer reviewing this on behalf of the vendor, not the client — is this clause a problem, and specifically, what's the worst realistic way it could be used against us? |
This isn't about asking the model to role-play for its own sake. Specifying whose interests it's reasoning from changes what counts as a risk, which is exactly the information the first version left out.
5 · Concise — Cut everything that isn't load-bearing
The opposite failure also happens: a prompt padded with backstory, hedging, and detail that doesn't actually change what a good answer looks like. Every extra sentence the model has to process is a sentence competing for attention with the parts that matter.
| Before | After |
|---|---|
| So I've been thinking about this for a while and I'm not totally sure how to phrase it, but basically I guess what I'm trying to ask is whether you think it would be a good idea, or maybe not a good idea, to switch our email tool to something else, considering we've been using the current one for a couple years now. | Should we switch email tools after two years on our current one? What would justify the switching cost? |
Nothing in the first version was wrong, exactly — it just buried one clear question under several sentences of throat-clearing. Cutting it doesn't lose information; the information wasn't there to begin with.
6 · Combine — When you're not sure which one applies
Most real prompts don't fit neatly into just one of the five categories above — a request can be simultaneously ambiguous and under-contexted, or clear but overlong. When you can't immediately tell which failure mode you're looking at, a general pass that checks for ambiguity, missing context, and unnecessary length together gets you most of the way there, even without picking a single technique upfront.
| Before | After |
|---|---|
| Write something for our newsletter about the new feature. | Write a 150-word newsletter blurb announcing our new bulk-export feature, for existing customers who've asked for it before. Lead with the capability, not the backstory of why we built it. |
This rewrite touches Clarify (which feature, what format), Elaborate (who's reading it, why it matters to them), and Concise (150 words, lead with the capability) all at once — which is normal. The six techniques are angles on the same prompt, not mutually exclusive modes.
Doing this without rewriting by hand every time
Applying these consistently is mostly a matter of habit, and habits are exactly what tend to slip under time pressure. That's where one-click rewriting tools become useful — MindMarks' own Optimizer sits next to the chat input on ChatGPT, Claude, and Gemini, and offers all six as selectable modes:
- Type your prompt as a rough draft — don't try to pre-optimize it.
- Click Optimizer next to the input box.
- Choose the mode that matches what's wrong with the draft, or use Auto if you're not sure.
- Review before sending. Rewrites aren't always perfect; Undo restores your original if the result misses what you meant.
Worth knowing: the Optimizer uses your AI quota like any other request. Auto mode is included in the free 50-per-month allowance.
Frequently Asked Questions
Related Articles
Export any conversation in two clicks.
MindMarks adds per-conversation export to ChatGPT, Claude, and Gemini — Markdown, JSON, PDF, or text, straight to your machine. It also gives your chat history folders, tags, and search.