The seven-line brief that makes AI feel less generic.

01 / Why the average answer appears

The model can only use the brief it gets.

When the request could belong to anyone, the answer usually does too.

“Write me a landing page” leaves out the audience, the promise, the proof, and the action. The model fills those gaps with familiar patterns. That is how you get a technically reasonable page with no reason to remember it.

A brief does not need magic syntax. It needs the missing decisions: who this is for, what should change for them, and what the work must not do. Write those down before asking for polish.

02 / The seven useful inputs

Give it seven handles to grab.

Use this compact structure as a starting brief—not a rigid formula.

Identity says who the AI should be for this job. Audience says who will use the result. Goal names the change you want. Output specifies the shape of the deliverable. Tone sets how it should feel. Constraints define boundaries. Reference gives a concrete example or source to learn from.

You do not have to fill every field every time. Start with the ones that would most change the answer. If a detail is important enough that you would correct a human collaborator for missing it, include it in the brief.

• I — Identity · A — Audience · G — Goal · O — Output
• T — Tone · C — Constraints · R — Reference

03 / Direct the second draft

Your second prompt is an edit, not a restart.

Keep the useful parts. Name the one change that would make the next version better.

Choose what is working, point to what is not, and offer material the tool could not have inferred. Then ask for a revised version. This keeps the work moving toward your taste instead of snapping back to the average.

Try the builder below. Copy the brief into your tool, review the result, then come back and change just one field. Notice how a better constraint can improve the work more than a longer prompt.