Open the exact workroom, tool, or prompt bank.

Best used when: Use before drafting anything important.

Act as my practical AI work partner. Before you draft anything, ask me the 5–7 questions that would most improve the final output for this task: [TASK]. My audience is [AUDIENCE]. The final output needs to be [FORMAT]. After I answer, create the finished deliverable.

Best used when: Use when you have scattered notes.

Turn these messy notes into a clean work brief. Create: 1) purpose, 2) background, 3) key points, 4) decisions needed, 5) open questions, 6) action items with owners/dates, and 7) a polished summary I can send. Notes: [PASTE NOTES].

Best used when: Use when a process lives in your head.

Create a beginner-friendly SOP from this rough process: [PASTE PROCESS]. Include purpose, when to use it, tools needed, step-by-step instructions, decision points, common mistakes, quality check, and what “done” looks like.

Best used when: Use when leadership needs the point fast.

Create a one-page executive brief for [TOPIC]. Include: what happened, why it matters, current status, risks/blockers, decision needed, recommendation, next steps, and a 3-sentence verbal summary.

Best used when: Use when a message is too harsh, vague, or emotional.

Rewrite this message so it is clear, warm, firm, and professional without sounding robotic. Keep the main request intact. Add a subject line if needed and give me 2 tone options: direct and diplomatic. Text: [PASTE].

Best used when: Use when you need repeatable execution.

Build a practical checklist for [TASK/PROCESS]. Organize it into before, during, after, and final QA. Include owner, timing, materials needed, and warning signs that something is missing.

Best used when: Use to improve AI output before using it.

Review this draft against the goal: [GOAL]. Score it 1–5 for clarity, completeness, tone, accuracy risk, and usefulness. Then revise it to meet a professional standard. Draft: [PASTE].

Best used when: Use when you repeat the same type of task.

Create a reusable mini prompt bank for my role: [ROLE]. I often need help with: [TASKS]. Create 10 copy-ready prompts with fill-in fields, when to use each, and what the finished output should look like.

Best used when: Use for policies, notes, research, or transcripts.

Synthesize this source material for [AUDIENCE]. Create: executive summary, key themes, important details, decisions or implications, open questions, and a short action plan. Stay grounded in the source and flag anything that needs verification. Source: [PASTE].

Best used when: Use when you want the writing to still sound like you.

Rewrite this in a clearer, more polished version while preserving my voice. Do not make it generic or overly formal. Improve structure, flow, and confidence. Text: [PASTE].

Best used when: Use when choosing between versions.

Compare Draft A and Draft B for clarity, tone, completeness, persuasion, and reader usefulness. Tell me which is stronger, what each is missing, and create a final blended version. Draft A: [PASTE]. Draft B: [PASTE].

Best used when: Use to turn expertise into instruction.

Turn these notes into a practical training guide for a beginner. Include learning objectives, plain-language explanation, step-by-step process, examples, practice activity, common mistakes, and final checklist. Notes: [PASTE].

Best used when: Use for sensitive replies.

Help me respond to this situation professionally. Goal: [GOAL]. Audience: [AUDIENCE]. Tone: calm, clear, respectful, and firm. Create 3 options: soft, balanced, and direct. Situation/message: [PASTE].

Best used when: Use for business or project thinking.

Write a strategy memo for [TOPIC]. Include context, goal, constraints, options, tradeoffs, recommendation, first steps, success measures, and risks to watch. Keep it practical, not theoretical.

Best used when: Use before publishing or sending.

Audit this document for missing information, weak logic, vague language, repeated sections, unsupported claims, and unclear next steps. Then give me a prioritized fix list. Document: [PASTE].

Best used when: Use for help centers or training pages.

Using only this source material, create a user-friendly FAQ with 15 questions and answers. Group the questions by theme, keep answers concise, and flag anything the source does not clearly answer. Source: [PASTE].

Best used when: Use inside Outlook.

Summarize this email thread into an action table. Include topic, decision or request, owner, due date, waiting-on item, suggested reply, and anything I should verify before sending.

Best used when: Use after a Teams meeting.

Create a meeting recap from this Teams meeting. Include key decisions, action items with owners and deadlines, open questions, risks/blockers, and a follow-up message I can post or email.

Best used when: Use inside Word.

Transform this document into a [memo/SOP/brief/checklist]. Keep the meaning accurate, add clear headings, remove repetition, and include a final review checklist for names, dates, facts, and next action.

Best used when: Use inside Excel.

Review this workbook/table and answer: [QUESTION]. Show the result as a summary table, explain how you found it, flag data quality issues, and suggest the next workbook question to ask.

Best used when: Use to make a deck from a doc.

Create a PowerPoint outline from this Word document. Audience: [AUDIENCE]. Goal: [GOAL]. Include slide titles, 3 bullets per slide, speaker notes, suggested visuals, and appendix items.

Best used when: Use for notes and repeated answers.

Organize these OneNote notes into summary, themes, decisions, action items, FAQ items, SOP candidates, and resources to save for later.

Best used when: Use Friday or Monday.

Create my weekly Microsoft 365 briefing from recent email, meetings, chats, and files. Include priorities, waiting-on items, meetings needing follow-up, deadlines, decisions, and suggested next actions.

Best used when: Use before sending.

Review this Copilot output for accuracy risk, unsupported assumptions, privacy or permission concerns, missing context, names/dates/numbers, tone, and final next action. Tell me what to revise before I use it.

Best used when: Use when inbox is overwhelming.

Act as my inbox triage assistant. Review this list of emails/messages: [PASTE]. Create a table with priority, reason, response needed, suggested action, deadline, and draft reply starter.

Best used when: Use when you need a gentle nudge.

Write a warm professional follow-up to [PERSON] about [ITEM]. Context: [CONTEXT]. Tone: friendly, clear, and not apologetic. Include a specific next step and deadline if appropriate.

Best used when: Use when delay is causing a problem.

Write a firm but respectful follow-up about [ITEM]. Include why it matters, what is needed, the deadline, and what will happen next if no response is received. Keep it professional.

Best used when: Use when an issue needs leadership attention.

Draft an escalation message for [ISSUE]. Include background, impact, what has already been tried, decision needed, recommended next step, and a concise subject line.

Best used when: Use before a meeting.

Create a meeting agenda for [MEETING]. Include purpose, desired outcome, topics, decisions needed, prep needed, time estimates, and a closing action-item review.

Best used when: Use after a meeting.

Turn these meeting notes into a professional recap. Include summary, decisions, action items with owners/dates, open questions, risks, and a follow-up email. Notes: [PASTE].

Best used when: Use for open loops.

Create a waiting-on tracker from this list: [PASTE]. Columns: item, person/owner, date requested, due date, current status, next follow-up date, risk if delayed, and follow-up message.

Best used when: Use to reduce messy communication.

Create practical Teams communication norms for [TEAM]. Explain when to use chat, channel posts, email, meetings, files, @mentions, urgency labels, and recaps.

Best used when: Use for work or business trackers.

Design an Excel/Sheets tracker for [PURPOSE]. Include columns, dropdown values, date fields, status logic, conditional formatting rules, sample rows, and a weekly review routine.

Best used when: Use when you know what you want but not the formula.

I am using [Excel/Google Sheets]. My columns are: [COLUMNS]. I need to calculate: [RESULT]. Give me the best formula, where to place it, how it works, and a quick test example.

Best used when: Use before summarizing messy data.

Review this spreadsheet structure: [PASTE HEADERS/SAMPLE]. Create a cleanup plan for duplicates, blank cells, inconsistent names, date formatting, categories, merged cells, and validation rules.

Best used when: Use for a summary tab.

Create a dashboard plan for this tracker: [PURPOSE + COLUMNS]. Include KPI cards, charts, filters/slicers, summary tables, warning flags, and a plain-language monthly summary.

Best used when: Use before creating pivots.

I need a pivot table that answers: [QUESTION]. My columns are: [COLUMNS]. Tell me rows, columns, values, filters, grouping, and the exact insight this pivot should reveal.

Best used when: Use to make priority visible.

Create conditional formatting rules for this tracker: [PURPOSE + COLUMNS]. Include overdue items, high priority, completed, waiting, missing owner, and due within 7 days.

Best used when: Use before sharing.

Audit this spreadsheet design: [PASTE HEADERS/SAMPLE]. Identify formula risks, missing columns, unclear statuses, duplicate fields, hard-to-read layout, and what to fix before sharing.

Best used when: Use after you have results.

Turn these spreadsheet results into a plain-language summary for [AUDIENCE]. Include what changed, what stands out, what needs attention, and recommended next steps. Data: [PASTE].

Best used when: Use for formal requests or documentation.

Draft a professional letter for [PURPOSE]. Audience: [AUDIENCE]. Include clear opening, brief context, specific request, supporting details, requested next step, and polished closing.

Best used when: Use for approvals or reimbursements.

Create a concise approval memo for [REQUEST]. Include background, amount/cost if applicable, reason, policy or business purpose, decision needed, deadline, and short email version.

Best used when: Use for repeatable work.

Create an SOP for [PROCESS]. Include purpose, when to use it, owner, tools, step-by-step process, decision points, common mistakes, escalation path, and final checklist.

Best used when: Use when teaching someone a process.

Turn this process into a training guide for a beginner. Include overview, why it matters, steps, visual notes or screen-capture spots to add, practice activity, knowledge check, and completion checklist. Process: [PASTE].

Best used when: Use to condense a long document.

Create an executive summary from this content. Include main point, key findings, implications, recommendations, risks, and next steps. Content: [PASTE].

Best used when: Use for formal recap.

Turn these meeting notes into clean minutes. Include attendees, purpose, topics discussed, decisions, motions/approvals if any, action items, owner, due date, and next meeting notes. Notes: [PASTE].

Best used when: Use for repeated documents.

Create a reusable Word/Docs template for [DOCUMENT TYPE]. Include headings, bracketed fill-in fields, example wording, instructions for each section, and final review checklist.

Best used when: Use before sending.

Edit this document for clarity, flow, tone, grammar, missing details, repetition, and next action. Then provide a polished final version and a short change summary. Document: [PASTE].

Best used when: Use before creating slides.

Act as a presentation strategist. I need a deck about [TOPIC] for [AUDIENCE]. Goal: [GOAL]. Ask me 5 questions, choose the best deck type, and recommend slide flow, tone, length, and what belongs in appendix.

Best used when: Use for leadership updates.

Create a 6-slide executive status deck for [PROJECT]. Include: snapshot, progress since last update, key metrics, risks/blockers, decisions needed, and next steps. Make every slide title a takeaway, not a topic.

Best used when: Use when someone needs to approve or choose.

Create a decision slide for [DECISION]. Include context, options, pros/cons, tradeoffs, risk of no decision, recommendation, decision owner, and requested deadline.

Best used when: Use for long reports.

Turn this report into a slide deck for [AUDIENCE]. Extract the main story, 5–7 slide titles, key bullets, visuals, speaker notes, and appendix items. Report/source: [PASTE].

Best used when: Use for teaching a process.

Create a training deck for [SKILL/PROCESS]. Include learning objectives, why it matters, step-by-step teaching slides, example/demo slide, practice activity, knowledge check, recap, and facilitator notes.

Best used when: Use for an offer or pitch.

Create a sales deck for [OFFER]. Audience: [AUDIENCE]. Include problem, cost of staying stuck, solution, what is included, outcomes, proof, objections, pricing/next step, and closing invitation.

Best used when: Use after slide outline exists.

Create speaker notes for this deck outline. Make the notes natural, confident, and concise. Include transitions between slides and a closing statement. Outline: [PASTE].

Best used when: Use to fix weak slide titles.

Rewrite these slide titles into takeaway headlines. Each title should tell the audience what to understand or decide. Keep titles short and business-ready. Titles: [PASTE].

Best used when: Use before designing slides.

For each slide below, recommend the best layout: timeline, comparison, process, dashboard, quote, before/after, table, chart, or story slide. Explain why and suggest a visual. Slides: [PASTE].

Best used when: Use before presenting.

Prepare me for questions about this presentation. Create likely questions, strong answers, sensitive questions to handle carefully, and a backup data list. Topic/deck: [PASTE].

Best used when: Use for live trainings.

Create a webinar deck plan for [TOPIC] lasting [LENGTH]. Include section timing, slide flow, engagement questions, demo moments, practice activity, Q&A, and follow-up resource slide.

Best used when: Use before sharing.

Audit this deck for storyline, slide order, title strength, audience fit, repetition, missing decision, visual overload, timing, and next action. Deck outline/slides: [PASTE].

Best used when: Use before files multiply.

Design a Google Drive folder system for [ROLE/PROJECT/BUSINESS]. Include main folders, subfolders, file naming rules, owner rules, sharing permissions, and examples of where common files go.

Best used when: Use for reports, guides, or letters.

Turn these notes into a polished Google Doc for [AUDIENCE]. Include headings, concise paragraphs, table if useful, action items, and a clear next step. Notes: [PASTE].

Best used when: Use for tracking requests or projects.

Create a Google Sheets tracker for [PURPOSE]. Include columns, dropdown values, conditional formatting, sample rows, protected columns to avoid editing, and a weekly review process.

Best used when: Use to collect consistent info.

Create a Google Form for [INTAKE/REQUEST/SURVEY]. Include title, description, questions, question types, required fields, branching if needed, and confirmation message.

Best used when: Use after collecting form data.

Design the workflow after form responses arrive. Include response Sheet helper columns, status values, owner assignment, follow-up templates, summary dashboard, and review rhythm.

Best used when: Use to manage meetings and follow-ups.

Create a Gmail and Google Calendar routine for [ROLE]. Include daily review, meeting prep, follow-up blocks, email templates to save, and weekly open-loop review.

Best used when: Use after Google Meet.

Turn these Meet notes into a recap with summary, decisions, action items, owner, deadline, open questions, and follow-up email. Notes: [PASTE].

Best used when: Use for source-based learning/content.

Using these sources/notes, create a grounded summary, study guide, FAQ, glossary, and content outline. Flag anything not clearly supported by the source. Source: [PASTE].

Best used when: Use before a tracker.

Create a project brief for [PROJECT]. Include purpose, desired outcome, stakeholders, scope, not-in-scope, timeline, milestones, owners, dependencies, decisions needed, and first 10 actions.

Best used when: Use to clarify who does what.

Build an owner matrix for [PROJECT/EVENT]. Include workstream, task, accountable owner, support person, due date, status, communication channel, and escalation path.

Best used when: Use for launches or events.

Create a timeline for [PROJECT/EVENT] from [START DATE] to [END DATE]. Include milestones, task groups, dependencies, owner roles, reminder points, and final QA week.

Best used when: Use for interviews, visiting speakers, trainings, or events.

Build a coordination plan for [EVENT/INTERVIEW]. Include invite list, schedule, room/virtual link needs, materials, reminders, day-of checklist, follow-up, and thank-you messages.

Best used when: Use for new team members, residents, clients, or members.

Create an onboarding tracker for [AUDIENCE]. Include phases, tasks, owner, due date, required documents, training items, access needs, check-in dates, and completion criteria.

Best used when: Use for status reports.

Write a leadership update for [PROJECT]. Include snapshot, completed work, upcoming work, blockers, decisions needed, timeline impact, and recommended next action.

Best used when: Use when work moves to another person.

Create a handoff plan for [ROLE/PROJECT]. Include current status, key contacts, files/links, recurring tasks, open loops, deadlines, risks, and first-week priorities for the new owner.

Best used when: Use after a planning meeting.

Turn these meeting notes into a workplan. Include decisions, tasks, owners, dates, dependencies, follow-up messages, and what should go into the tracker. Notes: [PASTE].

Best used when: Use to create budget structure.

Create budget categories for [PERSONAL/BUSINESS/PROJECT]. Include fixed, variable, one-time, recurring, savings/reserves, notes, and a monthly review checklist.

Best used when: Use for receipts and spending visibility.

Build an expense tracker for [PURPOSE]. Include columns, categories, receipt notes, payment method, tax/professional review flag, monthly summary fields, and sample rows.

Best used when: Use to understand money coming in.

Create an income/revenue tracker for [BUSINESS/PERSONAL]. Include date, source, offer/product/service, amount, payment status, platform, notes, and monthly summary.

Best used when: Use for offers/products/services.

Create a pricing scenario worksheet for [OFFER]. Include costs, time, platform fees, price points, sales volume, revenue goal, break-even estimate, and assumptions to verify.

Best used when: Use for timing pressure.

Create a monthly cash-flow snapshot for [PERSONAL/BUSINESS]. Include starting balance, expected income by date, expected expenses by due date, ending estimate, tight weeks, and action options.

Best used when: Use for recordkeeping.

Create a recordkeeping checklist for [TAX YEAR/PROJECT/BUSINESS]. Include income records, receipts, mileage/travel notes, subscriptions, software, contractor payments, missing items, and questions for a professional.

Best used when: Use monthly.

Turn this money data into a plain-language monthly review. Include income, expenses, top categories, unusual items, cash-flow concerns, questions to verify, and next month focus. Data: [PASTE].

Best used when: Use before meeting a professional.

Based on this situation: [PASTE], create organized questions for a qualified professional. Separate tax, accounting, legal, HR, and financial-planning questions where relevant. Do not give final advice.

Best used when: Use for repeated meetings.

Create a reusable meeting agenda template for [MEETING TYPE]. Include purpose, attendees, prep, agenda items, decisions needed, time blocks, action review, and follow-up section.

Best used when: Use for difficult updates.

Create an escalation message template for [ISSUE TYPE]. Include subject line, background, impact, actions taken, decision needed, recommended next step, and fill-in fields.

Best used when: Use for process documentation.

Create a reusable SOP template with fill-in fields, section instructions, example wording, common mistakes, troubleshooting, and final QA checklist.

Best used when: Use for approvals or choices.

Create a decision memo template for [DECISION TYPE]. Include context, options, recommendation, pros/cons, cost/timing, risks, requested decision, and signature/approval area.

Best used when: Use for help/customer/member messages.

Create 10 support response templates for [AUDIENCE]. Include warm greeting, issue acknowledgment, answer, next step, boundary language, and closing.

Best used when: Use for product/service launches.

Create a launch checklist for [OFFER]. Include pre-launch, content, emails, tech checks, payment links, member access, FAQ/support, launch day, and post-launch follow-up.

Best used when: Use for a vault/library.

Create a resource card template for [RESOURCE TYPE]. Include title, what it solves, when to use it, instructions, related prompts/templates, completion check, and update date.

Best used when: Use to show people what good looks like.

Create a completed example for this template: [PASTE TEMPLATE]. Fill it with realistic sample content and explain why each section is included.

Best used when: Use to organize channels.

Audit this Slack setup: [DESCRIBE CHANNELS]. Recommend what to keep, merge, archive, rename, and create. Include channel purpose, posting rules, and examples.

Best used when: Use for consistent updates.

Create Slack message templates for [TEAM/PROJECT]: weekly update, blocker, decision needed, quick request, announcement, handoff, and recap.

Best used when: Use to stop decisions getting lost.

Create a Slack decision-capture workflow. Include when to post, format, owner, decision log fields, follow-up, and how to move decisions into the project tracker.

Best used when: Use before building a database.

Design a Notion database for [PURPOSE]. Include properties, property types, views, filters, sorts, templates, sample entries, and weekly review routine.

Best used when: Use for command centers.

Create a Notion dashboard for [ROLE/BUSINESS]. Include sections, linked databases, views, quick links, daily/weekly review prompts, and rules to keep it simple.

Best used when: Use for knowledge hubs.

Design a Notion SOP and FAQ library. Include databases, properties, page templates, review dates, categories, search tags, and AI prompts to turn notes into resources.

Best used when: Use for clients/members/teams.

Create a Notion portal for [AUDIENCE]. Include welcome, start here, key links, timeline, resources, tasks, updates, support instructions, and privacy notes.

Best used when: Use for social/content planning.

Build a Notion content calendar for [BRAND/BUSINESS]. Include ideas, platform, format, status, publish date, assets, caption, repurposing notes, views, and weekly planning routine.

Best used when: Use at the start of the day.

Here is everything on my plate: [PASTE]. Sort it into must-do today, should-do this week, waiting-on, delegate, schedule, and later. Explain the top 3 priorities and why.

Best used when: Use Friday or Monday.

Run a weekly reset from this list: [PASTE TASKS/NOTES]. Create wins, open loops, overdue items, waiting-on items, next week priorities, meetings to prep, and follow-up messages.

Best used when: Use when things feel scattered.

Audit these open loops: [PASTE]. Group by owner, deadline, next action, follow-up needed, and risk if ignored. Create a clean tracker-ready table.

Best used when: Use to protect deep work.

Create a focus block plan for [TASK]. Include prep steps, distractions to remove, time block length, success definition, and what to do if interrupted.

Best used when: Use when tasks are vague.

Turn this task list into clear next actions. Each action should start with a verb, include owner, estimated time, due date if known, and first step. Tasks: [PASTE].

Best used when: Use before handing off.

Prepare a delegation brief for [TASK]. Include outcome needed, context, deadline, resources, constraints, quality standard, check-in point, and handoff message.

Best used when: Use when meetings take over.

Review these recurring meetings: [PASTE]. Recommend keep, shorten, combine, replace with update, or cancel. Include criteria and message templates.

Best used when: Use to upskill fast.

Create a 7-day learning sprint for [SKILL]. Include daily practice tasks, prompts to use, small deliverables, review questions, and one proof-of-skill artifact.