Specify the outcome, references, constraints, review points, and definition of done.
A good Work brief describes the result someone will use. Include the audience, exact output formats, source material, limits, and a test that proves the work is ready. State assumptions Work may make and which choices need your input.
Outcome: Create [deliverable] for [audience].
Context: Use [attached files or facts]. Preserve [details].
Format: Deliver [editable artifact] plus [export format].
Scope: Include [must-haves]. Keep this first version to [limit].
Review: Pause after [storyboard, outline, or prototype] so I can review it.
Done means: Check [specific tests] and explain anything incomplete.Upload the relevant source and identify its role: “Use this as factual source material” or “Match this visual style.” State which file is authoritative if several disagree. Work only has the context available in the task; do not assume it can see a file on your device that you have not attached.
For a short document, ask for a complete first draft. For a video, approve the storyboard and references before generating every clip. A requested pause is an instruction to Work, so check that it has reached the review point before approving the next phase.
For a game, list controls, collisions and restart. For a budget, give a known total. For a deck, ask it to inspect every slide. Request the actual files and an explanation of what was verified, rather than treating a confident completion message as proof.