These prompts are frameworks, not magic commands. Replace the bracketed details, provide relevant non-sensitive context, and review the response before using it. ChatGPT features can vary by plan and change over time.
1. Turn a Vague Goal Into an Action Plan
Act as a practical project planner. My goal is [goal]. My deadline is [date], available time is [hours per week], and constraints are [constraints]. Ask up to five essential questions first. Then create a prioritized plan with milestones, first actions, likely obstacles, and a weekly review checklist. Clearly label assumptions.
Best for: business owners, students, creators, and personal projects.
2. Prepare a Decision Brief
Help me compare [option A] and [option B] for [decision]. Use these criteria: [criteria]. Create a table showing benefits, risks, costs, reversibility, and missing information. Do not choose for me. End with five questions I should answer before deciding.
Quality check: Add your own criteria and verify any factual comparison.
3. Improve a Professional Email
Edit the email below for clarity, respect, and brevity while preserving my meaning and voice. Audience: [recipient]. Desired outcome: [outcome]. Tone: [tone]. Flag any sentence that could be misunderstood, then provide a revised version under [word limit] words. Email: [paste email]
4. Build a Content Brief
Create a people-first content brief about [topic] for [audience]. Their main problem is [problem]. Include search intent, a distinct angle, questions to answer, evidence needed, examples to gather, a logical outline, and a checklist that prevents generic or unsupported claims. Do not write the article yet.
5. Learn Through Questions
Teach me [topic] at a [beginner/intermediate/advanced] level using questions. Start with a short diagnostic quiz. Ask one question at a time, respond to my answer with targeted feedback, and adapt the next question. Do not reveal the complete answer until I attempt it.
6. Review Code Without Rewriting Everything
Review this [language] code for correctness, security, readability, and edge cases. Explain the three highest-risk issues first with specific references. Suggest the smallest safe fixes and focused tests. Do not rewrite unrelated code. Context: [context]. Code: [paste code with secrets removed]
7. Create a Customer Interview Guide
Create a 30-minute interview guide for people who [audience description]. We want to learn about [problem], not sell a solution. Write neutral questions about current behavior, pain points, workarounds, costs, and decision factors. Identify leading questions to avoid and suggest follow-ups.
8. Analyze Feedback Themes
Analyze the anonymized feedback below. Group it into recurring themes, needs, positive signals, frustrations, and contradictory views. For every theme, cite supporting excerpts and note how confident you are. Do not invent percentages. Feedback: [paste anonymized feedback]
9. Run a Pre-Mortem
Imagine that [project] failed six months from now. Generate realistic reasons across strategy, execution, customers, technology, people, budget, and external factors. Rank them by likelihood and impact, then suggest one early warning sign and one prevention action for each.
10. Design a Weekly Review
Create a 20-minute weekly review for my role as [role]. My priorities are [priorities]. Include questions for progress, unfinished work, decisions, energy, learning, risks, and next-week commitments. Keep it practical and format it as a reusable checklist.
11. Convert a Process Into a Standard Operating Procedure
Turn the process below into a practical standard operating procedure for [team/role]. Separate purpose, prerequisites, numbered steps, decision points, quality checks, escalation conditions, and evidence of completion. Identify missing details instead of inventing them. Process notes: [notes]
Best for: documenting repeatable work without hiding unclear ownership.
12. Create Test Cases From Requirements
Review these requirements for [feature/process]. Create test cases covering normal use, boundaries, invalid inputs, permissions, failure recovery, accessibility, and security-sensitive behavior. For each test, state setup, action, expected result, and the requirement it verifies. Flag ambiguous or untestable requirements. Requirements: [text]
13. Prepare a Difficult Conversation
Help me prepare for a respectful conversation with [person/role] about [issue]. My goal is [outcome], and the facts I can verify are [facts]. Separate observations from assumptions, suggest neutral opening language, likely responses, useful questions, boundaries, and a follow-up plan. Do not diagnose motives.
14. Audit a Proposal for Hidden Assumptions
Audit this proposal before approval. List its explicit claims, hidden assumptions, dependencies, missing evidence, affected groups, failure modes, and decisions that would be difficult to reverse. Then create a short validation plan for the three riskiest assumptions. Proposal: [text]
15. Design an Accessible Content Checklist
Create an accessibility review checklist for [content/page/document] intended for [audience]. Cover structure, headings, link text, image alternatives, color dependence, reading clarity, keyboard use, captions, and error messages. Explain how each check helps users and identify items requiring human testing.
16. Diagnose a Recurring Operational Problem
Help me investigate this recurring operational problem without jumping to a solution: [problem]. Known examples: [examples]. First separate symptoms, possible causes, and missing evidence. Then create a cause-and-effect map, questions for the people doing the work, data to collect, and a small test that could disprove the leading explanation. Do not treat correlation as causation.
Quality check: Confirm the diagnosis with observations from the real workflow before changing it.
17. Create a Handover Plan for Important Work
Create a handover plan for [responsibility/project] moving from [current owner] to [new owner]. Include purpose, current status, recurring tasks, deadlines, access requirements, key contacts, decision history, known risks, unresolved questions, first-week priorities, and a checklist for confirming the new owner can operate independently. Flag any secrets or personal data that should be transferred through an approved secure channel instead of pasted here.
18. Review a Form for Completion and Error Risk
Review this form or intake questionnaire for [purpose] and [audience]. Identify unclear questions, unnecessary data collection, duplicate fields, missing instructions, likely user errors, accessibility concerns, and sensitive information that needs justification. Propose clearer wording and a short validation plan. Do not assume collecting more data is better. Form fields: [paste fields without real personal data]
19. Create a Decision Log From Messy Notes
Turn the approved notes below into a decision log for [project/team]. For each decision, record the decision, date, owner, context, options considered, evidence used, assumptions, expected result, review date, and conditions that would trigger reconsideration. Separate confirmed decisions from proposals and unresolved questions. Do not invent owners or dates. Notes: [sanitized notes]
20. Plan a Small Experiment Before a Major Change
Design a small, reversible experiment to test whether [proposed change] improves [desired outcome]. State the hypothesis, baseline, participants or sample, success and harm metrics, minimum duration, controls, data needed, stop conditions, and how results should be interpreted. Identify confounding factors and do not assume a positive result proves the change will work at full scale.
Review: Obtain appropriate consent and specialist review when an experiment could affect people materially.
21. Build a Data-Cleaning Review Plan
Create a review plan for cleaning this dataset before analysis: [describe columns and purpose; do not paste sensitive records]. Cover missing values, duplicates, invalid formats, outliers, inconsistent categories, units, date handling, potential bias, and transformations that could change meaning. For every proposed rule, explain the risk and require an audit trail. End with validation checks that compare cleaned data with the source.
22. Map an Exception-Handling Process
Map how [process] should handle exceptions before any automation is introduced. List expected inputs, common exceptions, rare high-impact exceptions, detection signals, immediate containment, decision owner, escalation route, response deadline, evidence to preserve, and recovery steps. Identify exceptions that require human judgment and do not invent policies that are not provided. Process notes: [approved notes]
23. Prepare a Knowledge-Base Article From a Resolved Issue
Turn this resolved issue into a reusable knowledge-base article for [audience]. Include symptoms, scope, prerequisites, verified cause, safe resolution steps, validation, rollback, escalation conditions, and related questions. Remove names, credentials, internal-only details, and unsupported conclusions. Clearly distinguish the confirmed solution from possible alternatives. Sanitized issue record: [record]
24. Design a Practical Approval Workflow
Design an approval workflow for [request or decision]. Define request information, eligibility checks, reviewers, decision criteria, conflicts of interest, service targets, evidence required, rejection reasons, appeal or reconsideration route, audit record, and emergency exceptions. Identify steps that should not be automated and explain why. Do not present this as legal or compliance advice.
25. Create a Source-Controlled Writing Plan
Help me plan a document about [topic] using only approved sources. Create a source-control plan with claims to support, source types needed, citation notes, sections that require verification, statements to avoid until verified, and a review checklist for unsupported claims. Do not draft the document yet or invent facts. Approved source list: [sources or source descriptions]
26. Build a Personal Knowledge Retrieval System
Design a simple knowledge retrieval system for my notes about [area]. Include folder or tag structure, naming rules, metadata to capture, review cadence, duplicate handling, privacy cautions, and example search questions. Suggest how AI can help summarize or connect notes while preserving links back to original sources. Do not recommend uploading private notes to an unapproved service.
27. Turn Customer Questions Into a Help Center Plan
Analyze these anonymized customer questions and create a help center plan. Group questions by user goal, identify missing documentation, propose article titles, define the first article to write, and list the exact evidence or screenshots needed. Do not invent product behavior. Questions: [paste anonymized questions]
28. Build a Meeting Follow-Up Action Register
Turn these meeting notes into an action register for [team/project]. Extract decisions, action items, owners, due dates, dependencies, open questions, risks, and follow-up messages. Separate confirmed commitments from suggestions. Flag any item that lacks an owner, deadline, or acceptance criteria. Notes: [sanitized notes]
29. Create a Risk-Based Training Plan
Create a training plan for [role/team] learning [skill/process/tool]. Start with the real tasks they must perform, common mistakes, safety or compliance risks, practice exercises, job aids, assessment methods, refresher timing, and manager coaching prompts. Keep the plan practical for [available time] and identify topics that require expert review.
30. Review a Public Page for Trust Signals and Clarity
Review this public web page copy for clarity, usefulness, trust signals, unsupported claims, confusing navigation, missing contact or policy information, and anything that could look thin or misleading. Suggest specific edits, but do not invent credentials, guarantees, testimonials, statistics, or experience. Page purpose: [purpose]. Copy: [paste copy]
31. Create a Service Recovery Response Plan
Help me create a service recovery plan for [customer/user issue]. Known facts are [facts], affected people are [audience], and constraints are [constraints]. Separate what we know from what we still need to verify. Draft a response plan with immediate acknowledgement, investigation steps, owner, timeline, compensation or correction options if applicable, internal notes, and follow-up checks. Do not admit fault beyond verified facts.
32. Refresh an Old Article Without Padding It
Review this existing article for a useful update. Identify outdated sections, unsupported claims, duplicate ideas, missing practical guidance, weak examples, broken assumptions, and places where a shorter explanation would be better. Suggest a focused refresh plan that improves usefulness without adding filler. Article: [paste draft or outline]
33. Build a Technical Onboarding Checklist
Create a technical onboarding checklist for someone joining [project/team]. Include required access, local setup, architecture overview, key workflows, coding or documentation standards, security cautions, first tasks, validation commands, common failure points, and who to ask for each area. Flag anything that should not be shared in plain text, such as credentials or private keys.
34. Build a Role-Specific Hiring Scorecard
Create a hiring scorecard for [role] on [team]. Include must-have skills, nice-to-have skills, practical work-sample tasks, behavioral signals, red flags, interviewer questions, scoring criteria, evidence required for each score, and bias checks. Do not infer protected characteristics or recommend illegal screening criteria.
35. Run a Meeting Retrospective Without Blame
Help me run a retrospective for [meeting or recurring workflow]. Use the notes below to identify what worked, what wasted time, unclear decisions, missing owners, follow-up gaps, and improvements for the next meeting. Separate process issues from individual blame and create three realistic experiments to test. Notes: [sanitized notes]
36. Draft a Product Requirement From User Evidence
Turn this user evidence into a focused product requirement for [feature/problem]. Include target users, problem statement, non-goals, user stories, acceptance criteria, edge cases, privacy or accessibility considerations, analytics to review, and open questions. Do not invent demand, priority, or technical feasibility. Evidence: [interviews, tickets, or observations]
37. Plan a Cross-Team Dependency Review
Help me prepare a dependency review for [project]. List every dependency by team, owner, due date, input needed, output expected, risk if late, fallback option, and decision that would unblock progress. Use only the information I provide, flag missing owners or dates, and create a short agenda for resolving the top three risks. Notes: [sanitized notes]
38. Turn Support Tickets Into Product Signals
Analyze these anonymized support tickets for [product or workflow]. Group recurring user goals, friction points, missing documentation, possible bugs, feature requests, and confusing language. For each theme, cite supporting ticket excerpts, identify evidence needed before acting, and suggest one low-risk next step. Do not invent ticket volume or severity. Tickets: [paste anonymized tickets]
39. Create a Practical Data Retention Checklist
Create a practical data retention checklist for [team/process] handling [data type]. Include why the data is collected, minimum fields needed, retention period to confirm, access owner, deletion trigger, exception handling, audit evidence, and questions for legal, privacy, or compliance review. Do not provide legal advice or invent policy requirements.
40. Build a Practical KPI Review Without Vanity Metrics
Review the KPIs for [team/project]. Separate outcome metrics, activity metrics, quality checks, leading indicators, and vanity metrics. For each useful KPI, define owner, data source, review frequency, action threshold, and how it could be gamed. Flag missing baselines and do not invent performance numbers. Current KPIs: [list]
41. Create a Customer Onboarding Risk Checklist
Create an onboarding risk checklist for [customer/user type] starting [product/service/process]. Cover prerequisites, access, training, data migration, common mistakes, support triggers, privacy cautions, success signals, and the first follow-up review. Separate must-have steps from optional improvements. Context: [notes]
42. Turn a Strategy Into 30-Day Execution Tasks
Turn this approved strategy into a 30-day execution plan. Break it into workstreams, owners, dependencies, first actions, decision points, communication needs, risk checks, and weekly review questions. Preserve the strategy's intent and flag goals that are too vague to execute. Strategy: [text]
43. Draft a Pricing Change Communication Plan
Create a communication plan for a pricing or packaging change affecting [customer group]. Include audience segments, verified facts, likely concerns, support-team talking points, timing, internal approvals, FAQ topics, and phrases to avoid. Do not invent prices, legal terms, customer impact, or guarantees. Context: [approved notes]
44. Explain a Budget Variance Without Guessing
Help explain a budget variance for [team/project]. Use only the numbers and notes provided. Separate confirmed causes, possible causes, missing evidence, one-time effects, recurring risks, and follow-up questions. Draft a short explanation for leadership that avoids blame and unsupported certainty. Data and notes: [paste approved summary]
45. Build an Internal FAQ for a Process Change
Create an internal FAQ for [process change]. Cover what changed, why it changed, who is affected, dates, required actions, exceptions, support route, training links, and feedback method. Mark any answer that requires policy, legal, finance, or security review before publication. Source notes: [approved notes]
How to Get Better Results
- Provide a real audience, goal, and constraint.
- Ask ChatGPT to label assumptions and uncertainties.
- Request a critique or verification checklist after the first response.
- Do not paste confidential information, passwords, or private customer data.