The prompt brief kit: goal, context, constraints, output, acceptance
A fixed structure for turning a vague ask into an executable brief.
The five-part kit
- Goal: what should be accomplished?
- Context: who is this for, and what background matters?
- Constraints: what must stay fixed or appear explicitly?
- Output: what shape should the answer take?
- Acceptance: how will you tell if the result is usable?
Short example
Instead of:
Summarize the client meeting.
Write:
Goal: produce weekly client meeting notes.
Context: the audience is a sales lead who only cares about progress, risks, and next steps.
Constraints: do not invent numbers; keep each section under two sentences.
Output: use four sections: progress, risks, open questions, next steps.
Acceptance: someone should know who owns what without replaying the recording.
Why this matters
This is not prompt ceremony. It is a way to define work so it becomes transferable and testable.