Prompt Engineering·Core Skills·6 min read·Sep 5, 2026

The Clarity Test

The four questions every clear prompt answers, plus a before/after checklist for turning vague requests into specific ones.

Four questions that separate clear prompts from vague ones

"Make it good" and "write a friendly, 80-word reminder email for a customer whose invoice is 10 days overdue" are the same request in spirit, but only one of them is answerable without guessing. Clarity means the model never has to fill in a blank you didn't mean to leave.

What task do you actually want done? (an action verb: summarize, compare, draft, list)
How should it be shaped? (length, format, structure)
Who is it for? (their background, what they already know)
Why does it matter here? (the context that makes one answer right and another wrong)

✕ Vague prompt

Explain how invoicing works.

Open in ChatGPT ↗

Invoicing is the process of billing a customer for goods or services rendered. It typically includes the seller's details, an itemized list of charges, payment terms, and a due date. Businesses use invoices to track revenue and maintain records for accounting purposes...

✓ Clear prompt

Explain to a freelancer who just signed up for Ledgerly why setting a due date and a late-fee rule on their first invoice matters. Two short paragraphs, practical tone, no accounting jargon.

Open in ChatGPT ↗

Setting a due date turns "pay whenever" into a real deadline your client can plan around: most freelancers see payments arrive noticeably faster once invoices have one. A late-fee rule (even a small 1.5% monthly charge) rarely gets triggered, but just having it listed makes clients treat your deadline seriously. Together, they take the awkwardness out of chasing payment: instead of sending an uncomfortable follow-up text, you just point to terms the client already agreed to.

Turning a vague ask into a clear one

Before → after

"How do I price my service?"

"I'm a freelance video editor with 2 years of experience doing YouTube edits. Suggest a per-video pricing structure for 10–15 minute videos, with a rationale for each tier, aimed at small creators with under 50K subscribers."

"My app is buggy, help"

"Users report the checkout button on our iOS app becomes unresponsive after adding a promo code. It started after our last release. List the 3 most likely causes in order of probability, and a quick way to test each one."

"Write a proposal"

"Write a one-page project proposal for redesigning a 12-page marketing site, aimed at a non-technical client. Include timeline, 3 pricing tiers, and what's out of scope. Confident but not salesy tone."

Where clarity usually slips

Slip → fix

Assuming the model remembers context it was never given

Restate the relevant background every time: "the model doesn't know what situation you mean" unless you say so.

Vague amounts: "a few tips", "a short summary"

Use numbers: "4 tips", "a 3-sentence summary".

Stacking unrelated questions into one prompt

Ask one thing, or number the sub-questions explicitly so none get skipped.

Unclear references like "fix this" or "make it better"

Name what "this" is every time you introduce it, especially after the first message in a thread.

A 10-second check before you hit send

Would a smart colleague who's never seen this project understand exactly what you're asking, just from reading the prompt? If you have to imagine them asking a follow-up question, answer it before you send, not after.