NEW – Expanded Prompt Library

Draft a reply to an email that needs to [GOAL, e.g. confirm Thursday and ask for the agenda by Tuesday]. The sender is [GENERIC ROLE, e.g. an outside consultant we work with often]. Tone: [WARM / NEUTRAL / FORMAL]. Keep it under [N] words and end with a clear next step.

Summarize this email thread into three parts: the decision (if any), the open questions, and who owes what by when. Keep every date and name exactly as written. [PASTE NON-CONFIDENTIAL THREAD]

Rewrite this message to stay firm on the request but warmer in tone, keeping every fact and deadline intact: [PASTE DRAFT]. Then tell me in one line what you changed.

Write a follow-up to someone who hasn’t responded about [THING], sent [TIMEFRAME] ago. This is reminder number [N] and the deadline is [DATE]. Warm but unmistakably clear that action is needed. Under 80 words, with a subject line.

Draft an email declining [GENERIC REQUEST] while preserving goodwill. Include [ALTERNATIVE, IF ANY]. The “no” must be clear with no false hope. Two short paragraphs.

Help me build a one-page email triage system. The kinds of mail I get: [GENERIC LIST, e.g. scheduling requests, vendor pitches, internal questions, executive requests]. Propose categories, response-time targets, and which ones deserve saved templates. Format as a simple reference table.

Write an out-of-office auto-reply for [N] days away. Point urgent matters to a colleague (I’ll add the name). Professional and warm, under 70 words.

Create a reusable email template for [RECURRING EMAIL TYPE, e.g. confirming interview logistics]. Use [BRACKETS] for the variable parts and include a subject line with brackets too. Tone: [DESCRIBE]. Under 120 words. Then list the variables at a glance.

Find 60-minute meeting windows that work across [CITIES]. Business hours are 8–6 local for everyone; prefer [CITY] mornings. Output a table showing each city’s local time per option, and flag any daylight-saving wrinkle I should verify.

Draft an email proposing these meeting slots: [TIMES WITH ZONES]. Ask each recipient for a first and second choice by [DEADLINE]. Format it so it can be answered in one line. Subject line starting “Scheduling:”.

Draft an email moving [MEETING] from [OLD TIME] to [NEW TIME]. This is the [Nth] reschedule, so acknowledge the inconvenience briefly without over-apologizing. No exclamation points. Under 100 words, plus one warmer alternate.

Draft a friendly reply asking a meeting requester for a one-line objective, the expected outcome, and any pre-read materials — framed as helping me find the right slot. Two sentences plus a sign-off.

Create a reusable template declining meeting requests my executive can’t take. Include bracketed slots for the alternative offered [DELEGATE / WRITTEN UPDATE / LATER QUARTER]. Gracious, final, no false hope, three sentences.

Help me sequence [GENERIC SCHEDULING PUZZLE, e.g. a half-day visit needing four meetings, a lunch, and a tour] with these constraints: [LIST]. Propose a schedule that satisfies them, flag any conflicts plainly, and list what I should confirm first.

Create an agenda for a [LENGTH]-minute [TYPE] meeting. Attendees: [GENERIC ROLES]. Topics: [LIST]. Put decision items before discussion items, include time allocations that fit the total length, and mark topic owners as [TBD] for me to fill in.

Here are recurring meetings I coordinate (generic): [LIST: name-type, length, frequency, headcount, purpose]. Identify which show signs of low value and why. For the worst two, draft a tactful note to the owner suggesting a review — shorter, less often, or retired.

Turn these rough notes into formal minutes. Sections: Attendees, Decisions, Discussion Summary, Action Items (owner + due date), Open Questions. Don’t invent or assume — anything ambiguous goes under Open Questions. [PASTE NOTES]

From these notes, pull only the action items into a table: Task, Owner, Due Date, Status (blank). Flag any task missing an owner or date. [PASTE]

Write the attendee recap email from these minutes: a two-line summary, action items as bullets with owners bolded, and a “reply by [DAY] with corrections” line. Under 150 words, subject line starting “Recap:”. [PASTE]

From these notes, write a three-sentence summary for a senior executive who wasn’t there: what was decided, what it changes or costs, and what needs their attention. No preamble. [PASTE]

I ran a meeting and couldn’t take proper notes. Here’s everything I remember, unordered: [BRAIN DUMP]. Organize it into draft minutes and create a “Please Confirm” list of the gaps, phrased as questions I can send to attendees.

Based on these minutes, draft the agenda for the follow-up meeting: open questions and overdue actions first, then new topics, with time allocations for a [LENGTH]-minute slot. [PASTE]

Here is a transcript from a routine, non-sensitive meeting (recorded with consent and per policy). Produce: (1) minutes in standard sections, (2) an action table, (3) a recap email. Don’t invent; ambiguities go to Open Questions. [PASTE]

Convert these minutes into clean decision-log entries. For each decision: date, the decision in one line, the owner, and a one-line rationale. [PASTE]

I need to create a [DOCUMENT TYPE] for [AUDIENCE] that accomplishes [PURPOSE]. Propose an outline with section headings and one line each on what they cover. Then list three things documents like this commonly forget to include.

Using the outline above, draft the “[SECTION]” section. Tone: [DESCRIBE]. Under [N] words. Use only the facts I’ve given you, and mark anything you’d need from me as [FILL IN].

Interview me to document a procedure I know well: [PROCESS]. Ask one question at a time. When you have enough, produce a numbered SOP a new employee could follow alone, with a “before you start” section and a “common mistakes” section.

Review this document as a sharp-eyed editor: inconsistent terminology, undefined acronyms, contradicting dates or numbers, and steps that assume unexplained knowledge. List each issue and its location. Do not rewrite. [PASTE]

Repurpose this finished document into: (1) a five-bullet summary for an intranet post, (2) a 100-word announcement email, and (3) three slide headlines. Keep all facts identical across versions. [PASTE]

Turn my notes into a briefing email for a busy executive: subject line starting “BRIEF:”, one bottom-line sentence, up to four bullets, and one “decision needed” line if my notes contain one. Nothing I didn’t include. [PASTE]

Rewrite this policy or procedure text in plain English a brand-new employee could follow, keeping every rule and requirement intact. Use short sentences and a numbered list where it helps. [PASTE]

Here’s a template our office reuses: [PASTE GENERIC TEMPLATE]. Critique what’s outdated, unclear, or missing compared to best practice for this document type, then produce an improved version with [BRACKETS] preserved.

Create a slide-by-slide outline for a [LENGTH]-minute presentation on [TOPIC] for [AUDIENCE]. For each slide: a point-making headline (not a label), 2–3 bullets, and one speaker note. Max [N] slides. The audience’s unspoken question is [QUESTION] — answer it by slide three.

Rewrite these slide headlines so each one makes a point instead of labeling a topic (e.g. “Expenses now take five minutes” rather than “New System Overview”): [PASTE HEADLINES].

Write speaker notes for these slides, conversational and paced to about [LENGTH] minutes total. One short paragraph per slide. [PASTE SLIDE CONTENT]

Turn this presentation into a one-page leave-behind handout with the key takeaways and any action items, formatted to print cleanly. [PASTE]

For a presentation on [TOPIC] to [AUDIENCE], give me five likely tough or skeptical questions and a suggested answer for each. Keep answers calm and concrete.

This slide has too much text: [PASTE]. Cut it to a point-making headline plus three bullets of six words or fewer, and move everything else into speaker notes.

For a slide about [CONTENT], suggest the clearest way to show it visually — a chart type, a simple diagram, or an icon list — and explain in one line why that choice fits.

I’m in [Excel / Google Sheets]. My layout: [DESCRIBE COLUMNS, e.g. A = dates, B = category names, C = amounts]. Give me a formula that [WHAT YOU WANT IN PLAIN ENGLISH], tell me where to put it, and explain how it works in one sentence.

Explain this inherited formula step by step in plain English, then list what would break it: [PASTE FORMULA]

This formula [PASTE] is returning [ERROR or WRONG RESULT]. The columns involved contain [DESCRIBE TYPES, e.g. dates in B, dollar amounts in D]. List the likely causes in order of probability and how to check each one.

I have a messy sheet with these problems (no data included): [DESCRIBE, e.g. names formatted three ways, blank rows, dates stored as text]. Give me a step-by-step cleanup plan using built-in features, in the order that avoids creating new problems.

I need to present [WHAT THE DATA SHOWS, e.g. monthly spending across five categories over a year] to [AUDIENCE]. Which chart type fits best and why? What’s the most common mistake with that chart, and what should the title say to make a point?

Help me design a spreadsheet to track [GENERIC PURPOSE, e.g. office supply orders]: what columns, what formats, which totals or checks to build in, and one tip to keep it from degrading into a mess after six months.

Here are my own observations from a report: [YOUR NOTES, e.g. supply costs up three months running, postage down by half]. Write a two-sentence summary for my manager highlighting what actually matters.

Create a reusable executive travel briefing template. Sections: trip purpose in one line; day-by-day schedule with locations and contacts as [BRACKETS]; per-meeting prep notes (who, what we want, one talking point); logistics (hotel, transport, confirmations); a “while you’re traveling” office-coverage note. Skimmable in a moving car — short lines, bold the times.

Create a run-of-show for [EVENT, LENGTH, ELEMENTS]. Table columns: time, item, owner [TBD], setup needs, and a “watch for” note per row. Build in buffer time and flag which segments historically run over.

Build a master checklist for [GENERIC EVENT/TASK], organized by timeline: one month out, one week out, day before, day of. Include and mark the five items people most commonly forget for this kind of event.

Compare these options (generic terms only — no vendor names or account details): [TERMS FOR EACH]. Build a table with these criteria: [cost, effort, flexibility, risk]. Recommend one, then give the strongest argument against your own recommendation.

Here’s my event plan (generic): [OUTLINE]. Assume it’s the day after and something went wrong. List the ten most likely failure points in order of probability, and for the top three, what I could do this week to prevent them.

For [EVENT], create a one-page day-of contingency card: if [SPEAKER LATE / TECH FAILS / FOOD SHORT / ROOM DOUBLE-BOOKED], then the immediate move, the backup, and who decides. Sized to print and fold in a pocket.

Build a hosting plan for [GENERIC VISIT, e.g. two senior visitors, one full day]: pre-visit confirmations, arrival logistics, an hour-by-hour host schedule, amenities, and a “don’t let these happen” list.

Draft an all-staff reminder about [POLICY OR ISSUE]. Assume good intent (people forget, they don’t rebel), give the reason in one line, include one bolded action, no corporate phrases, under 100 words, tone of a helpful colleague. Give me light, standard, and firm versions.

Rewrite this note to a senior person so it can be read and answered in 30 seconds from a phone between meetings: [GENERICIZED DRAFT]. The ask must be unmissable, with no hedging and no over-apologizing.

Draft a follow-up about [THE STUCK THING]: assume the delay has a good reason and say so briefly; make the impact concrete if it slips past [DATE], without drama; end with the easiest possible next step for them. Warm, brief, zero guilt-trip vocabulary.

Draft an announcement of [UNPOPULAR, NON-HR CHANGE, e.g. the parking lot closes for two weeks]. Lead with the practical impact on the reader, give the reason honestly, the workaround clearly, and where questions go. No spin, no cheerfulness about the inconvenience. Under 150 words.

Here’s what I want to say, honestly and bluntly: [YOUR UNSENDABLE VERSION]. Translate it into something professional that keeps 100% of the substance and 0% of the temperature. Show me what you changed so I can see the technique.

Help me write a [retirement note / work-anniversary message / thank-you] for a colleague. True specifics: [2–3 REAL DETAILS, no full names needed]. Warm and genuine, no greeting-card clichés, under 120 words. Then a 30-word version for a group card.

Two teams keep colliding over [GENERIC PROCESS ISSUE, e.g. who books the large conference room]. Draft a neutral note proposing a simple rule, framed so neither side reads it as a loss. Include the rule, the reason, and a trial period.

Draft an announcement about [GENERIC CHANGE]. Audience: all staff. The main goal is that people remember the ONE key action: [ACTION]. Under 150 words, scannable, no buzzwords. Format: subject line, short intro, bolded key action, brief closing.

Draft a weekly status update to [STAKEHOLDERS] on [PROJECT]: state plainly whether we’re on track in line one, list workstreams as bullets, and put the next deadline up top. Brief, teammate tone, no last-paragraph burials.

Help me set up a simple task tracker for [PROJECT]: which columns, which statuses, and how to flag at-risk items. Keep it low-maintenance and explain how to keep it current in under five minutes a day.

Create a kickoff meeting agenda for [PROJECT OR INITIATIVE]: goals, roles, timeline, risks, and next steps. Time-boxed to [LENGTH], with owners marked [TBD].

For [GENERIC PROJECT], list the ten most common risks and an early warning sign for each, so I know what to watch for before they become problems.

Draft a clear note handing off [TASK] to [ROLE]: what’s needed, the deadline, the context they’ll need to do it well, and how to reach me with questions. Friendly and unambiguous.

Draft a friendly check-in asking [ROLE] for a status on [DELIVERABLE] due [DATE], framed as offering help rather than nagging. Under 70 words.

Help me write a short project wrap-up from my notes: what was delivered, what went well, what I’d improve, and any open items. Keep it to one page. [PASTE NOTES]

Here’s something AI helped me do at work: [PLAIN DESCRIPTION]. Rewrite it two ways: (1) a one-line entry for my wins log with a time estimate, and (2) a résumé/review-ready bullet using strong professional verbs (identified, built, established, trained).

Create a one-page guide teaching a coworker how to [SPECIFIC AI TASK, e.g. turn messy notes into clean minutes]. Plain steps, one copy-paste example prompt, and one “watch out for this” tip. Friendly and non-condescending.

Help me prepare to discuss my AI work in a performance review. Here are my wins: [PASTE WINS LOG]. Group them into themes, translate them into business value, and draft three sentences I can actually say out loud about taking on this role and where I’d like to grow it.

Draft a short memo requesting that my employer fund [TOOL] at [PRICE]/month. Include: the specific limit I’m hitting on the free version, estimated time saved per week on [TASKS], the return-versus-cost framing, and an offer to share what I build with the team. Confident and concise, under 200 words.

I’m a [ROLE, e.g. executive assistant] with [X] years of experience. List the skills from this role that become MORE valuable as offices adopt AI tools, and explain why in one sentence each.

Outline a 30-minute, low-key session teaching office colleagues practical AI basics. Audience: mixed skill, some nervous. Cover one mindset shift, two genuinely useful techniques they’ll use tomorrow, and the data-safety basics. Include a simple takeaway handout outline.

Ask me five questions, one at a time, to help me figure out where I could become more visibly useful with AI in my specific workplace — then suggest two concrete, low-risk first moves based on my answers.