Give your next prompt a proper brief.

01 / Name the job and the useful result

Describe a task you repeat, such as turning meeting notes into actions or drafting a customer reply. State what makes a good result: a short table, a response under 150 words, or a list of unresolved questions.

Bring an example of the input and, if you have one, an example of an output you liked. A long role description will not compensate for missing task details.

02 / Fill the five parts

A role is an instruction about approach. It does not give a model real qualifications or guarantee expert accuracy. This version replaces the original exaggerated expert claims with practical task requirements.

• Context: the situation, relevant facts, constraints, and source material.
• Role: the perspective or skills that would help with the task.
• Action: the steps to perform and when to ask questions.
• Format: the structure and length of the answer.
• Target audience: who will use or read the result.

03 / Make a vague request concrete

Instead of “summarize this meeting,” try: “For the project team, extract decisions and next actions from these notes. Use a table with action, owner, and due date. Mark missing owners or dates as unresolved. Do not assign them yourself.”

The improvement is in the observable requirements. You can look at the result and check whether the assistant followed them.