Turn a Vague Request into an AI Task Brief
On this page
“Help with my project” gives an assistant very little to work with. A task brief turns that broad wish into a small job with a visible finish line. You will learn to define a deliverable before asking the assistant to produce it. This is especially useful when a response sounds helpful but leaves you with nothing you can use.
Practice time: About 15 minutes. Use any text-based AI assistant you already have access to. Interface names and available tools vary. The examples below are fictional, and you do not need a paid plan or private information to practise.
Start with a small, clear example
A community group needs a one-page volunteer welcome sheet. The confirmed facts are: arrival at 9 am on Saturday, meeting point at the library entrance, comfortable shoes recommended, and questions directed to the volunteer coordinator. No phone number, lunch arrangement or finish time has been supplied.
Try this prompt
Copy the following into your assistant. Keep the sample input attached to the request so the task can be understood without guessing. Treat the response as a draft to inspect, not as a finished answer simply because it sounds confident.
Create a task brief for a one-page volunteer welcome sheet using only these confirmed facts: Saturday arrival 9 am; library entrance meeting point; comfortable shoes recommended; questions go to the volunteer coordinator. Include audience, deliverable, required facts, missing information and acceptance checks. Do not draft the sheet yet. Do not invent contact details or a finish time.
Work through the result
Read the proposed audience first. It should be new volunteers, not experienced organisers. Then inspect the deliverable: one page of welcome information is different from a recruitment advert.
Separate confirmed facts from missing facts. A useful brief should flag the calendar date, finish time and coordinator contact method as questions rather than quietly filling them in. Add a final check that every stated instruction can be traced to a supplied fact.
Only after reviewing the brief should you ask for the welcome sheet. This two-step process reduces wasted rewriting because you can correct the purpose and boundaries before they shape the whole draft.
Catch the common mistakes
Do not treat a long brief as a good brief automatically. Ten invented requirements are worse than four accurate ones. Avoid asking the assistant to “make reasonable assumptions” for details that determine where people go or when they arrive.
Check before you reuse it
Compare the response with your original input. Look for a missing condition, a changed number and any information the assistant added without support. Read names, dates and instructions particularly carefully. If the task involves an action, distinguish a suggested action from one you have actually completed.
Revise one specific weakness at a time. A follow-up such as “keep the uncertain date marked unconfirmed” gives a clearer correction than “make it better.” Keep the useful parts and check the revised passage again. An improved format does not guarantee improved accuracy.
Try it yourself
Write a brief for a beginner guide to borrowing a library book. You know the audience has a library card, but you do not know the library's loan period or late-return rules. Which facts should the brief request rather than assume?
Check your answer
The brief should identify the output as a short borrowing guide and request the local loan period, renewal process, borrowing limits and return rules. Those details belong to the library's actual policy. A strong acceptance check is “no local policy appears unless a source or confirmed input supports it.”
Keep exploring: AI learning path.