A useful AI task begins with a clear finish line. “Help with the board meeting” leaves most of the decisions unstated. “Draft a two-page board brief from these three files, with sources for every financial figure” gives the agent something concrete to work toward.
Describe what done looks like
Name the output, its audience and the level of detail. Say whether you need an editable document, a spreadsheet, a presentation or a short answer. Include the parts that must be present and anything that would make the result unusable.
A length limit can help, but a content limit is often more valuable. Ask for the three decisions the reader needs to make, the assumptions behind a forecast or the risks that need an owner. These instructions give the work a purpose.
Supply sources and boundaries
Point the agent to the relevant files and explain which source should take precedence when they disagree. Distinguish confirmed facts from ideas that are still being explored.
Draft a two-page board brief using the Q3 results sheet and the meeting notes in this project. Write for directors who have not read the source material. Include performance, risks and decisions needed. Cite each financial figure. Flag conflicting information. Keep the originals unchanged and do not send the draft.This is an example brief, not a promise of a particular result or completion time. The quality of the output depends on the source material, the task, the available tools and your review.
Review the plan and permission requests
Before the work moves beyond the intended scope, check what the agent proposes to read and change. A draft document and a sent message have different consequences. Review the destination and recipients when a task involves another app.
If the plan contains an unnecessary step, narrow the task. If the sources are missing, supply them or ask the agent to identify the gap. It is better to make uncertainty visible than to get a polished answer built on assumptions.
Review the result in layers
- First, check that the requested files exist and open in the expected editors.
- Next, verify names, dates, totals and source references.
- Then, read for omissions, unsupported conclusions and contradictory statements.
- Finally, check the format and tone from the recipient’s point of view.
Give specific feedback for the next pass. “The risks section needs owners and dates” is easier to act on than “make it better.” Keep the parts that already work and ask for focused changes.
Repeat only after the task works once
When a task becomes routine, consider turning it into a repeatable workflow. Keep the inputs, checks and review points explicit. A recurring job still needs a way to surface missing data or a result that needs attention.
For a closer look at permission boundaries, read Choose what your agent can reach. The strongest brief combines a useful outcome with a clear scope and a review you can actually perform.
