Start with the outcome
Say what you need, who it is for, and what a successful answer should contain. Add constraints such as tone, length, format, or source material when they matter.
- Name a role only when it adds useful context.
- Provide the inputs the answer must use.
- Ask for a format you can review quickly.
Copy-and-adapt examples
Rewrite this rough brief into a clear project plan. Ask me up to five questions first, then return milestones, risks, and the next action.
Review the text below for accuracy, missing assumptions, and unclear claims. Return a table with the issue, why it matters, and a suggested revision.
Improve the second draft
Treat the first response as a draft. Point out what is missing, add a check for unsupported assumptions, and revise against the original goal.
Choose a prompt by use case
For planning, give ChatGPT the decision, deadline, people involved, and constraints. For analysis, provide the source material and ask it to separate evidence from inference. For learning, state your current level and request practice rather than a lecture. For brainstorming, define the audience and ask for options with trade-offs so the list becomes useful.
- Planning: milestones, dependencies, risks, and next actions.
- Analysis: claims, evidence, uncertainty, and missing information.
- Learning: explanation, worked example, practice task, and feedback.
- Decision support: options, criteria, assumptions, and a recommendation.
Make the output easy to check
A prompt becomes more reliable when the answer has a visible structure. Ask for headings, a table, numbered steps, or a short decision record when you need to review several points. If the model lacks information, tell it to mark the gap instead of filling it with a confident guess.
When to use a follow-up prompt
Use a second instruction to challenge the draft: ask which requirement was missed, which claim needs evidence, and what assumption could change the result. This is more useful than simply asking for a longer answer. Keep the original brief in view while revising.
Six prompts to try and adapt
Project plan from rough notes
Turn the notes below into a two-week project plan. Ask up to three clarifying questions first. Return milestones, owner, dependency, risk, and next action. Mark any missing date as unknown.
Adapt it: Replace the time window, team roles, and required output columns.
Meeting decision record
Review this meeting transcript and return decisions, unresolved questions, action owners, and due dates. Separate explicit decisions from suggestions and quote no more than five words from the source for each item.
Adapt it: Add the decision rules your team uses and the fields needed in your tracker.
Research comparison
Compare these three options against cost, setup time, risk, and expected benefit. Use only the supplied evidence, identify missing data, and finish with a conditional recommendation.
Adapt it: Change the criteria weights and ask for a different audience such as a finance lead or beginner.
Learning coach
Teach me the basics of this topic as a 30-minute lesson for a beginner. Explain one concept, show one worked example, give me a short exercise, then grade my answer using three clear criteria.
Adapt it: Set your current level, topic, available time, and preferred practice style.
Customer reply draft
Draft a calm and helpful reply to this customer message. Acknowledge the concern, state what is known, avoid promises we cannot keep, and finish with one clear next step in under 140 words.
Adapt it: Insert the real policy, customer context, and tone boundaries before using it.
Assumption check
Review the draft below before publication. List factual claims, unsupported assumptions, unclear wording, and missing audience context. Suggest a revision for each issue without changing the intended meaning.
Adapt it: Add the review standard and the source documents that the model is allowed to use.
Frequently asked questions
What makes a ChatGPT prompt useful?
It states the task, supplies relevant context, and defines the shape or quality bar of the answer.
Should every prompt include a role?
No. Use a role when domain perspective or audience changes the result; otherwise, a clear task and context are enough.