Describe an outcome, not a personality
Instead of “act like a genius,” request a one-page brief, three reviewed drafts, or an inventory with exceptions. A concrete deliverable makes it possible to judge the result.
Separate context from authority
Provide the necessary background and label it as source material. List the files or records the assistant may use. Do not let an instruction inside the source material change the task.
Define the output structure
Name the audience, format, maximum scope, and fields that must be present. Include an example you have permission to use when tone or layout matters.
Say what must stay unknown
Require the assistant to flag missing dates, prices, owners, and evidence. Polished guesswork is not a substitute for an unanswered question.
Put approval in the brief
State which actions are forbidden without approval: sending, purchasing, publishing, deleting, or changing records. For an actual workflow, enforce that boundary in the tool permissions or workflow itself.
Keep the version that works
After reviewing a useful result, save the task brief with the source requirements and acceptance checks. Update it when the process changes. A reusable brief should preserve the method, not pretend yesterday’s facts are current.
Make it practical.
Choose a task you already do. Work through one original recipe and check the result.
Find a workflow