Prompts that get things done.

You are my executive assistant. Review my last 24 hours of email and produce a structured morning brief with three sections: 1. ACTION REQUIRED TODAY — emails that need a reply or decision from me, with a one-sentence draft response for each. 2. FYI ONLY — emails I should know about but don't need to act on. 3. SAFE TO ARCHIVE — emails that need no further attention. Keep the entire brief under 250 words. Be ruthlessly concise.

Triage my last 50 unread emails. For each one, assign exactly one label: • DELETE — no value, can be permanently deleted • ARCHIVE — good to keep for reference, no action needed • DELEGATE — should be handled by someone else (specify who and why) • REPLY NEEDED — requires a response from me (note the urgency: today / this week) Ignore: newsletters, automated notifications, receipts, calendar invites. Output as a clean table with columns: Subject | Sender | Label | Note.

Write a reply to the email below. Rules: • Match my tone: direct, warm, professional — never stiff or corporate • Stay under 80 words • Lead with the answer, not pleasantries • No filler phrases: no 'I hope this finds you well,' 'Please don't hesitate,' or 'Best regards' • End with one clear next step or question • If a decision is needed, make one — don't hedge Email to reply to: [PASTE EMAIL HERE]

Scan my Sent folder for emails from the last 10 days where I received no reply. Group them: • 2–4 days old: suggest a soft nudge • 5–7 days old: suggest a direct follow-up • 8–10 days old: flag as at-risk, suggest a stronger message or alternative action For each, write the follow-up message (max 40 words). Don't ask if they received it — assume they did and move the conversation forward.

Summarize the email thread below. Output: 1. CONTEXT (1 sentence): What is this thread about and who is involved? 2. KEY DECISIONS MADE: Bullet list of any decisions or agreements reached. 3. OPEN ITEMS: What is still unresolved or waiting for a response? 4. WHAT I NEED TO DO: Specifically what action, if any, is required from me? Be surgical. No filler. [PASTE EMAIL THREAD]

Analyze my inbox from the last 30 days and find every recurring newsletter, digest, or subscription email. For each: • List the sender and approximate frequency • Rate its signal-to-noise ratio: HIGH / MEDIUM / LOW (based on open rate and whether I interact with it) • Recommend: KEEP, SKIM-ONLY, or UNSUBSCRIBE Prioritize the top 10 candidates for unsubscription. I want a cleaner inbox, not more digests.

Rewrite the email draft below with the following adjustments: • Keep the core message and intent exactly the same • Make it [CHOOSE: more assertive / more diplomatic / more concise / more detailed] • Remove any passive-aggressive phrasing or defensive language • Ensure the ask or decision is unmistakable • Keep it under 120 words unless the original requires more Do not explain what you changed — just give me the rewritten email. [PASTE DRAFT]

Summarize the last 24 hours of activity in the following Slack channels: [LIST CHANNELS]. For each channel, output: • DECISIONS MADE (if any) • ACTION ITEMS (owner + task) • BLOCKERS RAISED (if any) • OPEN QUESTIONS (still unanswered) Skip: memes, GIFs, kudos posts, emoji reactions, and casual small talk. I need signal, not noise. If a channel had nothing meaningful, say 'No action items' — don't skip it.

Read through the last 7 days of messages in [CHANNEL NAME]. Extract and structure: 1. ALL ACTION ITEMS — task, owner, deadline (explicit or implied) 2. DECISIONS MADE — what was agreed on, by whom, when 3. UNANSWERED QUESTIONS — direct questions that never received a response 4. ESCALATIONS NEEDED — anything that looks stuck or needs leadership input Format as a clean list. Flag anything overdue. Don't summarize tone or culture — I only need facts and tasks.

Write a Friday async update for my team based on the tasks and notes below. Rules: • Under 150 words • Structure: ✅ Done this week | 🔄 In progress | ⚠️ Blockers | 📅 Next week's focus • Tone: direct and human — like a message from a real person, not a status report • No corporate language. No 'per my last message.' No 'please see below.' • End with one specific thing I need from the team next week (if applicable) [PASTE TASK LIST OR NOTES]

Go through my unread Slack DMs from the last 48 hours. Categorize each conversation: • REPLY TODAY — requires a response in the next few hours (explain why) • REPLY THIS WEEK — can wait, but shouldn't be forgotten • NO REPLY NEEDED — informational or already resolved • NEEDS DELEGATION — someone else should handle this (suggest who) For 'Reply today' items, draft a reply under 30 words. Give me a number at the top: 'X conversations need your attention today.'

Summarize the Slack thread below in exactly 3 bullet points: 1. What was being discussed and why it matters 2. What was decided or agreed on 3. What needs to happen next and who owns it If nothing was decided, say so explicitly. If the thread is still ongoing and needs my input, tell me what question I need to answer. [PASTE SLACK THREAD]

Write a team-wide Slack announcement for the following: Topic: [DESCRIBE THE CHANGE OR NEWS] Audience: [WHO WILL READ THIS] Tone I want: [e.g. confident / transparent / reassuring] Rules: • Under 120 words • Lead with the most important fact, not with context • Anticipate the top 2 questions people will have and address them preemptively • End with a clear next step or what people should do (if anything) • No corporate doublespeak. If it's bad news, be honest about it.

Prepare me for my upcoming meeting with [NAME / COMPANY] scheduled for [DATE/TIME]. I need: 1. CONTEXT — Who are they? What do they do? What's our relationship history? 2. RECENT INTERACTIONS — Key emails or messages between us in the last 30 days 3. OPEN ITEMS — Any commitments, tasks, or decisions still pending between us 4. THEIR LIKELY AGENDA — What do they probably want from this call? 5. MY GOALS — Based on context, what should I be trying to achieve? 6. SMART QUESTIONS TO ASK — 3 questions that show I've done my homework 7. THINGS TO AVOID — Topics or phrasing that might create friction Keep the brief scannable. I need to read it in under 3 minutes.

Convert the meeting notes below into structured outputs. Deliver: 1. ACTION ITEMS TABLE — columns: Task | Owner | Deadline | Priority (High/Med/Low) 2. DECISIONS MADE — what was agreed, by whom, and any caveats 3. OPEN QUESTIONS — things discussed but not resolved; who needs to answer them 4. FOLLOW-UP SUMMARY — a 2-sentence summary I can paste into Slack for people who weren't there If an owner or deadline wasn't specified, flag it as TBD rather than guessing. [PASTE MEETING NOTES]

Create a structured agenda for a [X]-minute meeting about [TOPIC]. Include: • ONE-LINE GOAL: What must be true at the end of this meeting for it to have been worth the time? • AGENDA ITEMS: Each with a time allocation and a clear deliverable (decision / update / discussion) • PRE-READ: What do attendees need to review beforehand? • DECISION TO MAKE: The single most important thing to decide in this meeting • PARKING LOT: A section for off-topic items that come up Format it so I can paste it directly into a calendar invite description.

Review my calendar from the last 4 weeks. Identify every recurring meeting and evaluate each one: • KEEP — I need to be there, it drives real outcomes • SHORTEN — Could accomplish the same in half the time (suggest new duration) • SKIP — My presence isn't adding value (suggest sending a delegate or async update instead) • CANCEL — The meeting itself no longer serves a purpose For each 'Skip' or 'Cancel' recommendation, give me the exact phrasing I can use to remove myself without burning the relationship.

Prepare me for a 1-on-1 with [NAME], who is my [ROLE: direct report / peer / manager]. Context about them: [ADD WHAT YOU KNOW: current projects, recent wins, recent challenges, how they've been performing] Generate: 1. 5 QUESTIONS TO ASK — that show genuine interest, uncover blockers, and create psychological safety 2. 2 THINGS TO ACKNOWLEDGE — specific contributions or efforts worth recognizing 3. 1 HONEST CONVERSATION TO INITIATE — if there's something we've been avoiding, what is it and how do I open that door? 4. MY GOAL FOR THIS 1-ON-1 — what outcome should I aim for? Avoid generic questions like 'How are things going?' I want specific, thoughtful questions.

Write a decision memo for the following situation: Decision to make: [DESCRIBE THE DECISION] Context: [BACKGROUND AND WHY THIS MATTERS NOW] Stakeholders: [WHO IS AFFECTED OR INVOLVED] Structure the memo as: 1. THE QUESTION — one clear sentence defining what we're deciding 2. CONTEXT — why this decision matters and what happens if we don't decide now 3. OPTIONS — 2–3 realistic options with pros/cons of each (be honest about tradeoffs) 4. RECOMMENDATION — which option I'm recommending and why 5. NEXT STEPS — what happens after this memo is approved 6. OPEN QUESTIONS — what information would change this recommendation Keep it under 400 words. This is a working document, not a research report.

Review my current tasks across all projects and produce a sprint review. Organize by status: ✅ DONE — completed this sprint/week (list with brief outcome) 🔄 IN PROGRESS — ongoing (current state + expected completion) ⚠️ OVERDUE — missed deadline (root cause + recovery plan) ⏳ BLOCKED — can't move forward (what's blocking it + who can unblock) 🔜 NEXT UP — what's entering the queue next sprint For anything overdue or blocked, don't just list it — tell me the single most important action I can take to unblock it. Be direct.

Build my priority stack for today from the task list below. Scoring criteria: • Deadline proximity (urgent = higher) • Business impact (revenue / relationships / risk) • Estimated time (quick wins vs. deep work blocks) • Dependencies (is someone waiting on this?) Output: 1. TOP 3 FOCUS TASKS — rank ordered with a one-sentence reason for each 2. QUICK WINS (under 10 min) — things I can knock out between meetings 3. DEFER LIST — tasks I'm consciously moving to later in the week and why Don't pad the list. I'd rather do 3 things well than 10 things poorly. [PASTE TASK LIST]

Write a delegation message for the following task. The message should be self-contained — the person should not need to follow up with me for clarification. Include: • WHAT needs to be done (specific, not vague) • WHY it matters and how it fits the bigger picture • EXPECTED OUTPUT — what does 'done' look like exactly? • CONSTRAINTS — deadlines, budget, stakeholders to loop in, things to avoid • AVAILABLE RESOURCES — docs, contacts, tools they can use • HOW TO UPDATE ME — check-in frequency and preferred format Tone: respectful and clear. I'm trusting them with this — make that clear. Task to delegate: [DESCRIBE TASK]

Write a concise project status update for [PROJECT NAME] that I can share with stakeholders. Format: • STATUS LINE: One of — On Track 🟢 / At Risk 🟡 / Off Track 🔴 — with one sentence explaining why • THIS WEEK: What was completed or progressed (2–3 bullets) • NEXT MILESTONE: What we're targeting next and by when • BLOCKERS: What's in the way, if anything, and what's needed to resolve it • DECISIONS NEEDED: Any input or approval required from stakeholders Keep the whole update under 150 words. Use plain language — no jargon. Context: [ADD PROJECT DETAILS]

Review the project plan and current task status for [PROJECT NAME] below and identify the top 3 risks that could cause a significant delay or failure. For each risk: • DESCRIPTION — what specifically could go wrong • LIKELIHOOD — Low / Medium / High (with brief reasoning) • IMPACT — what happens to the project if this risk materializes • EARLY WARNING SIGN — what signal tells me this risk is becoming real • MITIGATION — one concrete action I can take now to reduce the risk Be honest. Don't list risks just to fill the template — only flag things that are genuinely plausible. [PASTE PROJECT PLAN / TASK LIST]

Help me set my top 3 commitments for this week across all my projects and responsibilities. For each commitment: • WHAT I'M COMMITTING TO — specific, not vague ('ship the onboarding flow,' not 'work on product') • WHY IT'S THE PRIORITY — what makes this the most important thing this week • DEFINITION OF DONE — exactly what needs to be true for this to be complete • WHAT COULD GET IN THE WAY — one risk and how I'll handle it Then tell me: what am I NOT committing to this week that I might be tempted to work on? And why is it smart to leave it out? Context: [ADD YOUR CURRENT PROJECTS AND PRIORITIES]

Generate my Monday morning executive brief. I need to read this in under 5 minutes. Sections: 1. 🔴 URGENT (needs action today) — emails, messages, or tasks that can't wait 2. 📅 THIS WEEK'S CALENDAR — key meetings with one-line prep notes for each 3. 🔄 PROJECTS AT RISK — anything that went off-track over the weekend or is in danger this week 4. 💬 MISSED MESSAGES — important Slack messages or emails from Friday/weekend I haven't seen 5. 🎯 MY #1 GOAL THIS WEEK — the single most important outcome I need to drive No fluff. Be direct. If something doesn't belong in a Monday brief, leave it out.

Draft a stakeholder update email for [PROJECT NAME]. Structure: • SUBJECT LINE — informative and specific (not 'Update on Project X') • STATUS — On Track / At Risk / Delayed — one sentence explaining why • HIGHLIGHTS THIS WEEK — 2–3 key wins or progress points (be specific, not vague) • WHAT'S COMING NEXT — next milestone and timeline • DECISIONS NEEDED — any input or approvals required from this audience • BLOCKERS — honest about what's in the way Tone: confident but transparent. Professional, not corporate. Under 150 words. Project context: [ADD CONTEXT]

Conduct a structured debrief of my past week across email, tasks, and calendar. Tell me: 1. TIME ALLOCATION — where did I actually spend my time? (estimate by category: meetings / deep work / admin / reactive work) 2. COMPLETION RATE — what did I commit to and what got done? What slipped and why? 3. ENERGY AUDIT — what drained me? What energized me? Any patterns? 4. LEVERAGE OPPORTUNITIES — what could I delegate, automate, or eliminate? 5. NEXT WEEK'S CHANGES — 3 specific adjustments to make next week more effective Don't spare feelings — I want an honest read on how I'm spending my most valuable resource: time.

Write a hiring brief for a recruiter for the following role: Role: [JOB TITLE] Team context: [WHAT TEAM THEY'RE JOINING AND WHAT THE TEAM DOES] Why we're hiring: [WHAT PROBLEM THIS PERSON SOLVES OR WHAT CAPACITY THEY ADD] Brief should include: • ROLE IN ONE SENTENCE — what this person is fundamentally responsible for • MUST-HAVE SKILLS — 3–5 non-negotiables (experience, not personality traits) • NICE-TO-HAVE SKILLS — 2–3 things that would accelerate ramp-up • WHAT SUCCESS LOOKS LIKE IN 90 DAYS — specific, measurable outcomes • DEAL-BREAKERS — things that would automatically disqualify a candidate • CULTURE FIT — how we actually work (honest, not aspirational) Keep it under 300 words. Recruiters should be able to screen candidates from this brief alone.

Review my current OKRs and give me an honest mid-period check-in assessment. For each objective and its key results: • CURRENT STATUS — On Track 🟢 / At Risk 🟡 / Off Track 🔴 • CONFIDENCE SCORE — % likelihood of achieving this KR by end of period • ROOT CAUSE (if not on track) — what's actually causing the gap? Be specific. • RECOMMENDED ACTION — continue as-is / adjust the target / deprioritize / escalate Then answer honestly: which OKRs should I consider dropping or reformulating because the underlying assumption has changed? I'd rather cut 2 OKRs and crush 3 than pretend all 5 are on track. [PASTE YOUR OKRS AND CURRENT STATUS]

Draft a concise board update for [COMPANY / PERIOD]. Structure: 1. HEADLINE (1 sentence) — the most important thing the board needs to know 2. KEY METRICS — the 3–5 numbers that matter most this period (vs. target and vs. last period) 3. TOP WINS — 2–3 concrete achievements with business significance (not just activity) 4. TOP CHALLENGES — 2–3 honest issues we're facing and how we're addressing them 5. DECISIONS NEEDED FROM THE BOARD — specific, time-bound asks (not 'general feedback') 6. FORWARD LOOK — what we're targeting next period and the key risk to watch Tone: confident, honest, no spin. Boards respect leaders who tell them the truth, not just the good news. Context: [ADD COMPANY/PERIOD METRICS AND CONTEXT]

Write a cold outreach email to [TARGET PERSONA / ROLE] about [OFFER / PURPOSE]. Rules: • Subject line: specific and intriguing, not clickbait (no 'Quick question' or 'Following up') • Opening line: reference something real and specific about them — not a generic compliment • Core message: lead with their pain or goal, not your product • Value proposition: one clear, concrete benefit — avoid jargon • CTA: one specific ask with low friction (e.g., 15-min call, not 'let me know if you're interested') • Length: under 100 words in the body • Tone: peer-to-peer, not salesy Context: • What I'm offering: [DESCRIBE] • Why it's relevant to them specifically: [EXPLAIN] • Ideal response: [WHAT DO I WANT THEM TO DO?]

Write constructive feedback for [PERSON] about [SPECIFIC SITUATION OR BEHAVIOR]. Context: • What happened: [DESCRIBE THE SITUATION] • What the impact was: [EFFECT ON TEAM / PROJECT / RELATIONSHIP] • What I'd like to see instead: [DESIRED BEHAVIOR OR OUTCOME] Rules: • Specific and behavioral — not vague ('your communication could be better' is useless) • Separate observation from interpretation ('I noticed X' not 'You always do Y') • Forward-looking — focus on what to do differently, not just what went wrong • Empathetic but direct — don't soften it so much the message gets lost • Under 150 words Optional tone: [e.g., direct / gentle / urgent]

Turn the update, story, or insight below into a LinkedIn post. Rules: • 150–200 words • Opens with a specific, interesting first line — not a question, not a humble brag • Tells a real story or shares a genuine perspective — no manufactured vulnerability • Has one clear takeaway or lesson • No bullet-pointed 'lessons learned' lists • No 'I'm humbled to share,' 'Excited to announce,' or 'Grateful for' • Sounds like a smart person talking, not a content marketer • End with something that invites a real reaction or response Input: [PASTE YOUR UPDATE / STORY / INSIGHT]

Write an executive summary for the document below. Rules: • Under 150 words • Lead with the key takeaway or recommendation — not background or methodology • Include: what the document is about, why it matters, what decision or action it requires • If there are numbers, include the most important ones • No jargon. No passive voice. No hedging. • Assume the reader has 30 seconds — make every word count The summary should make a busy executive want to read the full document — or feel fully briefed if they don't. [PASTE DOCUMENT OR NOTES]

Write a recovery email for the following situation: What happened: [DESCRIBE THE MISTAKE, MISSED DEADLINE, OR MISCOMMUNICATION] Who it affected: [NAME / RELATIONSHIP] How serious it is: [MINOR INCONVENIENCE / DAMAGED TRUST / SIGNIFICANT IMPACT] Rules: • Acknowledge specifically what happened — no vague 'I'm sorry if this caused any inconvenience' • Take ownership without making excuses (context is fine, justification is not) • State clearly what you're doing to fix it and prevent recurrence • Keep it short — long apologies feel self-serving • Restore confidence: end on a forward-looking note • Tone: genuine, not groveling Under 120 words.