Give the task, the context, and the finish line
Turn a vague prompt into a request you can evaluate.
In plain language
A useful prompt explains the task, supplies relevant context, and describes the output you need. Constraints such as audience, length and format make success easier to judge.
Use examples when they clarify what you mean. Keep confidential information out of tools unless you are authorized to share it. After the response, check the result against your requirements and revise the request if something is missing. Prompting helps steer behavior; it does not guarantee factual accuracy.
Instead of “Explain AI,” try “Explain AI agents to a nontechnical colleague in 120 words. Include one scheduling example, one limitation, and define any technical terms.”
Try it yourself
Rewrite a vague request with a task, audience, context and an output format you can check.
Go deeper · for developers and architects
For repeatable workflows, test prompts on representative cases, track versions and check regressions. A successful single example is not enough to establish reliability.
Check your understanding
2 related questions, with an explanation for each answer.
Explore the original sources
Microsoft beginner curriculum ↗Report an issue
Tell the editors what needs correcting. Reports are reviewed and do not automatically remove content. Do not include personal or confidential information.
Finished this lesson?
Completion records your choice, not a measured skill level.