AI Revolution AtlasAsk Dr. Mira
Menu

Reusable prompts

Prompt with purpose, context, and review

These templates help beginners ask clearer questions while keeping privacy, verification, and human responsibility in view.

20 minute readLast reviewed 2026-06-20

Plain-language summary

What this guide covers

A prompt is an instruction or question you give an AI tool. A good prompt states the goal, context, constraints, output format, and verification needs. These templates are designed for low-risk use and should be adapted with public, fictional, or approved information only. A prompt can improve the output, but it cannot guarantee truth or safety.

Why it matters

Blank prompts often produce vague answers. Overly detailed prompts can accidentally expose private information. A safe prompt gives enough context for the task while keeping sensitive data out and planning how the output will be checked.

What you will learn

  • Choose a prompt template by task type and risk level.
  • Edit variables without adding sensitive information.
  • Add verification and privacy steps to every important prompt.
  • Recognize when a prompt is unsuitable for a task.
  • Use prompts as drafts inside human-led workflows.

Guide section

Prompting principles

Prompting works best when the user defines the task and review plan.

Use every prompt with these rules

  • Start with a clear goal and audience.
  • Use public, fictional, de-identified, or approved information.
  • State constraints such as length, tone, format, and source boundaries.
  • Ask the model to flag assumptions, missing information, and claims to verify.
  • Check important output outside the model.
  • Do not use prompts to bypass policy, security, consent, school rules, workplace rules, or professional review.
  • Keep a person responsible for final use.
NeedTemplate groupBest forNot for
Work supportWork promptsLow-risk drafts, notes, checklists, and workflow thinking.Confidential, personnel, legal, financial, medical, or security matters.
LearningLearning promptsPractice, explanations, quizzes, and reflection.Hidden completion of assignments or collecting private student data.
WritingWriting promptsClearer drafts, tone checks, and plain-language edits.Deception, impersonation, fake reviews, or unsupported claims.
ResearchResearch promptsQuestion framing, source checking, and claim decomposition.Professional advice or relying on AI as the only source.
PlanningPlanning promptsLow-risk learning, career, and project plans.Major legal, financial, medical, safety, or employment decisions without qualified review.

Guide section

Work prompts

Use these only with public, fictional, or approved workplace information.

Meeting action items

Purpose: Turn safe notes into a draft follow-up.

Expected output: Decisions, action items, owners, dates, open questions, and uncertain points.

Iteration tip: Ask the model to separate confirmed items from items needing confirmation.

Verification step: Check names, deadlines, decisions, and commitments before sending.

Privacy warning: Do not include confidential, personnel, legal, medical, financial, security, customer, or child-related notes.

Unsuitable use: Do not use for sensitive meetings or official records without approved process.

Using these safe meeting notes, draft a follow-up for [audience]. Include confirmed decisions, action items, owners, due dates, open questions, and items needing confirmation. Do not invent decisions or commitments. Mark uncertainty clearly.

Editable fields: audience, safe-meeting-notes

Work email draft from approved facts

Purpose: Draft a low-risk email from facts the sender has approved.

Expected output: A concise draft with a clear next step.

Iteration tip: Ask for a warmer or more direct tone after checking facts.

Verification step: Confirm policies, promises, names, dates, and attachments.

Privacy warning: Do not include private customer, employee, client, medical, legal, or financial details.

Unsuitable use: Do not use to send legal notices, HR actions, medical advice, financial commitments, or crisis messages.

Draft a [tone] email for [audience] about [topic]. Use only these approved facts: [approved facts]. Include a clear next step. Do not invent promises, policies, prices, deadlines, or reasons. List anything I should verify before sending.

Editable fields: tone, audience, topic, approved-facts

Workflow bottleneck review

Purpose: Find bottlenecks and review points in a low-risk workflow.

Expected output: Steps, bottlenecks, risks, possible AI support, and human checkpoints.

Iteration tip: Ask the model to rank suggestions by risk before usefulness.

Verification step: Confirm the workflow with people who do the work.

Privacy warning: Use fictional or approved process notes only.

Unsuitable use: Do not use for regulated, safety-critical, HR, finance, health, legal, or security workflows without qualified review.

Review this low-risk workflow: [workflow name]. Steps: [safe steps]. Pain points: [pain points]. Identify bottlenecks, handoffs, risks, possible AI assistance, required human checkpoints, and success measures. Do not recommend full automation unless risks are low and review is clear.

Editable fields: workflow-name, safe-steps, pain-points

Decision checklist draft

Purpose: Create a draft checklist for a low-risk recurring decision.

Expected output: Criteria, required information, red flags, and escalation triggers.

Iteration tip: Ask what could go wrong if the checklist is used too mechanically.

Verification step: Have the decision owner review criteria and escalation points.

Privacy warning: Do not include personal records or sensitive case details.

Unsuitable use: Do not use for rights, benefits, employment, health, legal, financial, education-discipline, or safety decisions without official policy and qualified review.

Help draft a checklist for a low-risk decision: [decision]. Audience: [users]. Include required information, criteria, red flags, escalation triggers, and what not to decide by checklist. Mark assumptions and items needing policy review.

Editable fields: decision, users

Guide section

Learning prompts

Use these for practice and understanding, not hidden completion of assigned work.

Beginner explainer

Purpose: Explain a topic in plain language.

Expected output: Short explanation, example, key terms, and check questions.

Iteration tip: Ask for a simpler version or a different example.

Verification step: Compare facts with a trusted source.

Privacy warning: Use public topics, not private situations.

Unsuitable use: Do not use as a substitute for teacher instructions or professional advice.

Explain [topic] to [audience level] in clear language. Include one everyday example, three key terms with definitions, two common misunderstandings, and five self-check questions. Mark any facts I should verify.

Editable fields: topic, audience-level

Practice quiz

Purpose: Practice recall and understanding.

Expected output: Questions, answer key, explanations, and weak-area suggestions.

Iteration tip: Ask for easier or harder questions after answering.

Verification step: Check the answer key against course material or trusted sources.

Privacy warning: Do not paste private student records or graded work.

Unsuitable use: Do not use to cheat on tests or assignments.

Create a practice quiz on [topic] for [level]. Include [number] questions using a mix of multiple choice, short answer, and explanation questions. Provide an answer key with brief explanations and list what I should review if I miss each question.

Editable fields: topic, level, number

Mini learning plan

Purpose: Plan a short learning sprint.

Expected output: Weekly goals, practice tasks, evidence artifact, and reflection questions.

Iteration tip: Ask to reduce the time requirement if the plan is too large.

Verification step: Compare resource suggestions with official or trusted sources.

Privacy warning: Do not include sensitive personal details.

Unsuitable use: Do not use for licensing, medical, legal, financial, or urgent decisions without qualified guidance.

Create a [number]-week learning plan for [skill] for a learner who can spend [hours per week]. Use public or low-risk practice tasks. Include weekly goals, exercises, one evidence artifact, reflection questions, and safety checks. Do not promise outcomes.

Editable fields: number, skill, hours-per-week

Misconception check

Purpose: Find likely misunderstandings about a topic.

Expected output: Misconceptions, corrections, examples, and study prompts.

Iteration tip: Ask for misconceptions specific to beginners or a certain role.

Verification step: Check corrections against course material or trusted references.

Privacy warning: Use general learning needs, not private student details.

Unsuitable use: Do not use to diagnose a learner or make education-placement decisions.

List common misconceptions about [topic] for [audience]. For each one, explain the correction in plain language, give a safe example, and suggest one practice question. Mark any claims that need verification.

Editable fields: topic, audience

Guide section

Writing prompts

Use these to improve clarity while keeping facts, voice, and responsibility with the writer.

Plain-language rewrite

Purpose: Make a draft clearer and easier to read.

Expected output: Revised draft plus a list of changes.

Iteration tip: Ask for a version for a different audience.

Verification step: Check that meaning did not change.

Privacy warning: Do not paste confidential drafts into unapproved tools.

Unsuitable use: Do not use to remove required warnings, terms, citations, or policy details.

Rewrite this safe draft for [audience] at about an eighth-grade reading level. Keep the meaning, facts, and required details. Improve structure and clarity. After the rewrite, list what you changed and what I should verify.

Editable fields: audience, safe-draft

Tone check

Purpose: Check whether a message sounds respectful and clear.

Expected output: Tone risks, suggested edits, and revised draft.

Iteration tip: Ask for more direct, warmer, or more neutral options.

Verification step: Confirm the revised tone fits the real relationship.

Privacy warning: Replace private names and details before using.

Unsuitable use: Do not use to manipulate, impersonate, or hide responsibility.

Review this safe message for tone, clarity, and possible misunderstandings. Audience: [audience]. Purpose: [purpose]. Suggest edits that keep my meaning and voice. Do not add facts or promises. List any sentences that could sound harsh, vague, or too certain.

Editable fields: audience, purpose, safe-message

Outline builder

Purpose: Organize a draft before writing.

Expected output: Structured outline, missing questions, and source needs.

Iteration tip: Ask for a shorter outline if it is too complex.

Verification step: Check that each section has real support.

Privacy warning: Use only public or approved topic information.

Unsuitable use: Do not use to generate fake citations or unsupported arguments.

Create an outline for [document type] about [topic] for [audience]. Include purpose, section headings, key points, examples, source needs, and questions I must answer before drafting. Do not invent facts or citations.

Editable fields: document-type, topic, audience

Accessibility review for a draft

Purpose: Check a public-facing draft for accessibility and usability issues.

Expected output: Accessibility concerns and improvement suggestions.

Iteration tip: Ask for a version optimized for scanning or screen-reader clarity.

Verification step: Review against WCAG and human testing when needed.

Privacy warning: Do not include private user data.

Unsuitable use: Do not treat this as a formal accessibility audit or legal compliance opinion.

Review this safe public-facing draft for accessibility and usability. Check plain language, headings, link text, image descriptions needed, table clarity, reading order, and confusing instructions. Suggest improvements and list what should be manually tested.

Editable fields: safe-public-draft

Guide section

Research prompts

Use these to ask better questions and verify claims, not to replace research.

Claim decomposition

Purpose: Break a claim into parts that can be checked.

Expected output: Claim parts, source needs, assumptions, and uncertainty.

Iteration tip: Ask the model to rank claims by risk or importance.

Verification step: Check claims with trusted sources outside the model.

Privacy warning: Use public claims, not private allegations or sensitive records.

Unsuitable use: Do not use as the only source for legal, medical, tax, financial, or safety claims.

Break this claim into checkable parts: [claim]. For each part, say what kind of source would be needed, what assumptions are involved, what could be uncertain, and what would change the conclusion. Do not decide truth without evidence.

Editable fields: claim

Source quality review

Purpose: Evaluate whether sources fit a question.

Expected output: Source roles, strengths, limits, and gaps.

Iteration tip: Ask what source types are missing.

Verification step: Open and read the sources yourself.

Privacy warning: Do not include private documents unless the tool is approved.

Unsuitable use: Do not use to launder weak sources into strong claims.

Review these source descriptions for the question: [question]. Sources: [source titles and short notes]. For each source, identify source type, relevance, currency, possible bias, limits, and what claim it can support. Do not invent source content.

Editable fields: question, source-titles-and-notes

Research brief draft

Purpose: Draft a short brief from source notes.

Expected output: Summary, facts, uncertainty, source map, and next questions.

Iteration tip: Ask for a version with stronger caveats.

Verification step: Compare every factual sentence with the source notes.

Privacy warning: Use public source notes only.

Unsuitable use: Do not use for professional advice or high-stakes decisions.

Using only these source notes, draft a brief for [audience] about [question]. Include a short summary, key facts, source mapping, uncertainty, conflicting evidence if present, and next questions. Do not add facts not in the notes.

Editable fields: audience, question, source-notes

News sanity check

Purpose: Slow down before sharing a news claim.

Expected output: Check questions, source types, and sharing caution.

Iteration tip: Ask for what would be needed to verify the claim today.

Verification step: Check current reputable sources before sharing.

Privacy warning: Do not include private messages or allegations about private people.

Unsuitable use: Do not use to confirm breaking news without current source checking.

Help me sanity-check this public news claim before sharing: [claim]. Break it into checkable parts, list source types needed, identify emotional or manipulative wording, and write a cautious version that does not overstate what is known.

Editable fields: claim

Guide section

Planning prompts

Use these for low-risk planning where a person still owns the decision.

Career skill inventory

Purpose: Organize real skills and gaps.

Expected output: Proven skills, developing skills, examples, artifacts, and learning gaps.

Iteration tip: Ask for a shorter version focused on one role.

Verification step: Compare with real job postings and honest evidence.

Privacy warning: Use a non-sensitive summary, not a full private resume.

Unsuitable use: Do not use to create fake experience, fake credentials, or hidden keyword stuffing.

Using this non-sensitive experience summary, organize a truthful skill inventory for [target role]. Separate proven skills, developing skills, examples I can explain, possible evidence artifacts, and gaps to learn. Do not invent experience, tools, credentials, metrics, employers, or outcomes.

Editable fields: target-role, non-sensitive-experience-summary

Small project plan

Purpose: Plan a low-risk project.

Expected output: Goal, tasks, timeline, risks, checkpoints, and review plan.

Iteration tip: Ask to reduce scope if the plan is too large.

Verification step: Confirm deadlines, dependencies, and owner responsibilities with real people.

Privacy warning: Do not include confidential project details.

Unsuitable use: Do not use for safety-critical, legal, medical, financial, or regulated project decisions without qualified review.

Create a small project plan for [project] with [timeframe]. Include goal, audience, tasks, owners, dependencies, risks, human checkpoints, success criteria, and a review date. Use only the safe information provided and mark assumptions.

Editable fields: project, timeframe, safe-information

Personal learning sprint

Purpose: Plan a short learning sprint.

Expected output: Weekly practice, artifact, reflection, and safety checks.

Iteration tip: Ask for a version for beginner, job seeker, or employed learner.

Verification step: Check resources and credential claims independently.

Privacy warning: Keep personal constraints general.

Unsuitable use: Do not use to make expensive education or career decisions without additional human and official-source review.

Build a [duration]-day learning sprint for [skill]. I can spend [hours per week]. Include weekly practice, one artifact, reflection questions, feedback ideas, and safety checks. Do not promise results. List assumptions I should verify.

Editable fields: duration, skill, hours-per-week

AI use risk review

Purpose: Decide whether a task is suitable for AI support.

Expected output: Risk level, safer role for AI, checkpoints, and escalation triggers.

Iteration tip: Ask for a more conservative version.

Verification step: Check tool policy, data rules, and domain rules before acting.

Privacy warning: Describe the task generally; do not include sensitive details.

Unsuitable use: Do not use to approve high-stakes AI use by yourself.

Review this proposed AI use: [general task description]. Assess stakes, reversibility, sensitive data, error detectability, judgment required, affected people, and policy questions. Recommend whether AI should assist, automate with review, stay human-led, or not be used. List escalation triggers.

Editable fields: general-task-description

Difficult conversation prep

Purpose: Prepare for a respectful conversation without scripting deception.

Expected output: Goals, listening questions, points to clarify, and tone suggestions.

Iteration tip: Ask for a calmer or shorter version.

Verification step: Make sure the final words are yours and fit the relationship.

Privacy warning: Remove names and private details.

Unsuitable use: Do not use to manipulate, threaten, diagnose, or avoid urgent professional help.

Help me prepare for a respectful conversation about [topic] with [audience]. My goal is [goal]. Suggest opening points, listening questions, possible misunderstandings, and a calm closing. Do not script manipulation, threats, or false claims. Mark what I should decide myself.

Editable fields: topic, audience, goal

Decision options map

Purpose: Organize options for a low-risk decision.

Expected output: Options, tradeoffs, missing information, and next questions.

Iteration tip: Ask to add a no-action option.

Verification step: Confirm facts and consult qualified help for serious decisions.

Privacy warning: Keep details general and non-sensitive.

Unsuitable use: Do not use for legal, medical, tax, financial, safety, or emergency decisions.

Help map options for this low-risk decision: [decision]. Include options, benefits, risks, unknowns, people affected, information needed, and a next-step checklist. Do not make the decision for me. Mark any area needing qualified advice.

Editable fields: decision

Avoidable errors

Common mistakes and better approaches

Using a template without editing the variables.

Better approach: Adapt the goal, audience, constraints, output format, and verification step.

Adding private details to make the answer feel personal.

Better approach: Use safe summaries, fictional examples, or approved tools only.

Treating prompt output as final.

Better approach: Use the output as a draft, question list, or planning aid, then verify.

Using prompts for high-stakes advice.

Better approach: Escalate legal, medical, tax, financial, safety, emergency, or rights-related decisions.

Remember this

Key takeaways

  • A prompt should include goal, context, constraints, format, and verification.
  • Templates improve consistency but cannot guarantee accuracy or safety.
  • Use safe information only unless a tool and process are approved.
  • Every useful prompt should include a review plan.
  • Prompts should not bypass rules, policy, security, consent, or professional review.
  • The person using the output owns the final decision.
  • If a task feels sensitive or high stakes, use the safety page before prompting.

Questions readers ask

Frequently asked questions

Can these prompts guarantee correct answers?

No. They can improve clarity and structure, but every important output still needs verification and human review.

Can I paste my full resume, documents, or messages into a prompt?

Use caution. Do not paste private, confidential, student, employee, customer, medical, legal, financial, or sensitive information into unapproved tools.

How do I choose the right prompt?

Start with the task type: work, learning, writing, research, or planning. Then check whether the task is low risk. If it is sensitive or high stakes, use the safety framework first.

Should I tell people I used a prompt?

Disclosure depends on context, school rules, workplace policy, publication rules, and trust. When AI materially helped with public or shared work, it is often safer to explain what AI helped with and what a person reviewed.

Can I use these prompts with any AI tool?

The structure is general, but tools differ in settings, privacy practices, memory, retrieval, file handling, and output quality. Check the tool and policy before use.

Sources and review notes

Sources were accessed on the dates shown. Links open the original organization’s page.

  1. SRC-01
    Artificial Intelligence Risk Management FrameworkNational Institute of Standards and Technology · Published 2023-01-26 · Accessed 2026-06-20
  2. SRC-02
    Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence ProfileNational Institute of Standards and Technology · Published 2024-07-26 · Accessed 2026-06-20
  3. SRC-03
    Privacy FrameworkNational Institute of Standards and Technology · Accessed 2026-06-20
  4. SRC-04
    Artificial IntelligenceCybersecurity and Infrastructure Security Agency · Accessed 2026-06-20
  5. SRC-05
    Privacy and SecurityFederal Trade Commission · Accessed 2026-06-20
  6. SRC-08
    Artificial intelligence in educationUNESCO · Accessed 2026-06-20
  7. SRC-09
    AI PrinciplesOrganisation for Economic Co-operation and Development · Accessed 2026-06-20
  8. SRC-10
    Copyright and Artificial IntelligenceU.S. Copyright Office · Accessed 2026-06-20
  9. SRC-11
    WCAG 2 OverviewWorld Wide Web Consortium · Accessed 2026-06-20
  10. SRC-13
    Prompt engineering techniquesMicrosoft Learn · Published 2026-05-13 · Accessed 2026-06-20
  11. SRC-14
    Prompt engineeringOpenAI · Accessed 2026-06-20

Your next step

Choose a low-risk template

Pick one prompt for a safe practice task, then check the output using the safety framework.