AI Guides › Claude Mastery

The Difference Between A Good Prompt And A Good Brief

By Nigel Guy · 2 min read

A prompt can be well-written — clear sentences, correct grammar, a reasonable request — and still fail the moment a follow-up question arrives, because it never carried enough shape to survive one. A brief is built to survive follow-up; that's the actual distinguishing feature, not politeness or length.

What a brief has that a prompt usually doesn't

1. The use, not just the ask. What this is actually for, and who reads or uses the result.
2. The non-negotiable constraints, stated once. So a follow-up doesn't require restating the whole request from scratch.
3. An example of "done." Even rough, this does more work than another paragraph of description.
4. What's already been ruled out. So the response doesn't confidently suggest something you've already tried and rejected.

The mechanism for turning a prompt into a brief

1. Write your first draft as a normal prompt.
2. Ask yourself: if I handed this to a colleague with none of my context, what would they need to ask me before starting? Add those answers in.
3. Check it against "The One-Sentence Test" — can you restate the ask in one plain sentence? If not, the brief isn't finished yet.

What to skip

Skip writing brief-level detail for a trivial, one-off request — the setup cost is worth paying on anything you'll reuse or hand off, not on everything. And skip mistaking length for brief-quality; a long prompt with no stated use or constraints is still just a long prompt.

Guardrails

• A well-built brief still needs its output reviewed — clarity of the ask raises the odds of a good answer, it doesn't replace checking one.
• Save briefs that worked as templates for next time — that's the actual payoff for the extra minute spent building one properly.
• If you find yourself restating the same context every time you use a prompt, that's the signal it needed to be a brief from the start.

All 751 AI guides · JulieMango plans from £17/mo