Turn a task into a prompt with context, constraints, and an output format. Use it to make requests easier to follow and evaluate.
How to use
Sign in and state your goal. Add the input material, intended reader, required sections, and restrictions. Test the generated prompt with a small example.
Example
Ask for a prompt that turns meeting notes into a table with task, owner, deadline, and unanswered questions.
FAQ
Can a prompt grant access to files?
No. Attach the source material in the system where you use the prompt and check its available tools.
Related tools
A practical task
Write a small acceptance test for the prompt. For a task extraction request, give a sample note with one explicit deadline and one missing owner. The response should retain the deadline and mark the owner as unspecified, making errors easy to spot.
Another useful question
Should I request a role such as expert?
A role alone is vague. Add the source, actual constraints, required fields, and a concrete example of a good answer. Those details make the request testable.
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Context and audience | The same fact needs different explanation for a specialist and a first time reader. State the audience, purpose, and terms they already know. Relevant context guides wording more effectively than broad requests to make a text impressive. |
| Supplied facts | A writing request needs the facts the finished draft must preserve. Names, dates, quantities, and policies should come from your source. Missing information is a question to resolve rather than a blank to fill with a plausible invention. |
| Outline structure | A useful outline gives each section a distinct job and orders those jobs around the reader's question. Repeated headings with different keywords do not add coverage. Remove sections that cannot contribute a concrete answer. |
| Source boundaries | A summary or rewrite works from the material you provide. A URL alone does not supply the full article in this interface. Include the relevant passage and keep citations attached to the claims they support. |
| Editorial review | Review facts, names, omissions, and implications before approving a draft. A smooth sentence can still change a condition or attribute a statement to the wrong person. Compare meaning with the source instead of judging fluency alone. |
| Evidence and claims | A claim needs support separate from its confident wording. Keep source notes for numbers, comparisons, and factual statements. Removing a hedge does not turn an unverified statement into an established fact. |
| Tone and commitments | Tone changes the way a message sounds, not the obligations it contains. A friendly version must not invent permission, and a formal version must not invent a promise. Compare commitments as well as style. |