The best prompters don't get it right on the first try. They treat it as a conversation: get output, find the one thing most wrong, add one constraint to fix it, retry.
Most people give up after one try. Power users get what they want in 2–3 targeted patches — not full rewrites.
Round 1: "Write a 1-page proposal for migrating our Go monolith to microservices. Audience: CTO + VP Eng at a 60-person B2B SaaS. Cover: problem, solution, 3-phase timeline, outcomes, top 3 risks." → Good structure. Problem statement is too technical for the CTO.
Round 2: "Keep everything else. Rewrite ONLY the problem statement. Translate technical bottlenecks into business language: developer velocity and release frequency, not deployment pipelines." → Better. But risks section lists generic cloud risks, not ours.
Round 3: "Rewrite the risks section ONLY. Replace the generic risks with these specific ones: (1) our team has no Kubernetes experience, (2) the order schema is 6 years old and migration is complex, (3) a 6-week window where two codebases coexist." → Done. 3 surgical patches. Nothing that worked got overwritten.
Fast one-line patches to use after getting output — no full rewrite needed:
"Make this 35% shorter. Keep all key points, cut every filler sentence."
"The opening is too slow — delete sentence 1 and start with what's currently sentence 2."
"Rewrite ONLY the third paragraph. Add a specific dollar amount or time saving to make it concrete."
"Too formal. Rewrite as if sending this to a colleague on Slack, not presenting to the board."
"Give me 5 alternative versions of just the headline — different angles. I'll pick one."
"Add one real example (company, person, or number) to each bullet point."
Claude remembers context well. 'Keep sections 1 and 3 exactly as written. Rewrite section 2 only — make it more concrete with a specific example.'