Use when: You receive a vendor pitch, a resume, or a technical update full of buzzwords and need to know what it actually says.
Rewrite the text below into plain English. Remove all corporate buzzwords ("synergy," "paradigm," "leverage") and marketing fluff. Summarize the core message in exactly three bullet points:
1. What are they proposing?
2. What is the actual cost or request?
3. What is the specific benefit to us (if any)?
Use when: You have to review a long document (contract, proposal, policy) and are afraid of missing a red flag.
Act as a cynical lawyer who protects [Your Company's] interests. Review the attached text. Do not summarize it. Instead, extract the 5 most dangerous clauses, vague promises, or obligations that could hurt us later. For each, explain why it is a risk in one sentence.
Use when: You need to write a high-stakes document (strategy deck, quarterly review) and have been staring at a blinking cursor for 20 minutes.
I need to write a [Document Type] for [Audience]. The goal is to convince them to [Goal]. Do not write the document. Instead, give me a detailed, fill-in-the-blanks outline. Break it down into sections with bullet points indicating exactly what data or arguments should go in each block to make it persuasive.
Use when: You need someone to tell you the truth, not what you want to hear.
I'm about to [Action]. Act as a brutally honest advisor who cares about my success but won't sugarcoat anything. Tell me:
1. The one thing I'm probably overestimating
2. The one thing I'm probably underestimating
3. What I should do differently
Use when: Leadership asks about a new AI announcement and you need to explain it without sounding like a hype merchant.
Explain this in plain language for a busy manager:
[Paste article or announcement]
Separate into:
1. What it is (one sentence)
2. What's real vs. hype
3. Who should actually care (specific roles)
4. One low-effort way to experiment this week (or "safe to ignore for now" if appropriate)
Use when: You need to present the same update to different audiences (your team, your boss, the C-suite) and each one cares about completely different things.
I need to communicate the following update to three different audiences:
UPDATE: [Paste your update here]
Rewrite this update three ways:
1. FOR MY TEAM: Focus on what changes for them day-to-day. Be direct. Skip the corporate framing.
2. FOR MY MANAGER: Focus on timeline, risks, and what decisions are needed. Keep it under 100 words.
3. FOR LEADERSHIP: Focus on business impact, cost, and strategic alignment. No jargon. Two sentences max.
Use when: You got pulled into a meeting in 10 minutes and have no idea what it's about.
I have a meeting in 10 minutes about [Topic]. I know almost nothing about it.
Give me:
1. The 3 most likely reasons this meeting is happening
2. The 2 questions I should ask to sound informed
3. The 1 thing I should NOT say if I want to avoid getting assigned more work
Keep it under 100 words total.
Use when: Your boss wants a weekly status update and you'd rather do literally anything else.
Here are my rough notes from this week:
[Paste messy notes, Slack messages, or bullet points]
Turn these into a professional status update for my manager. Format:
COMPLETED:
- (2-3 items, outcome-focused, not task-focused)
IN PROGRESS:
- (2-3 items with expected completion dates)
BLOCKED:
- (Only if something is actually blocked. If nothing is blocked, skip this section entirely.)
Keep the total under 150 words. No filler. No "I'm pleased to report."
Use when: Before signing any AI vendor POC or contract. Forces vendors to get specific.
You are a skeptical IT Director evaluating a vendor. Read this description and give me three things:
1. THE JARGON DECODER: For every vague claim (e.g., "seamless integration," "flexible API," "enterprise-ready"), write one specific technical question that forces them to define the architecture.
2. TECHNICAL DEBT: Identify two integration questions their materials avoid answering, specifically around data privacy, security compliance, and long-term maintenance costs.
3. THE HYPE FILTER: Flag one red flag in their business model or pricing structure that suggests hidden costs or vendor lock-in after year one.
Give me all questions in plain language I can ask in a 30-minute demo.
[PASTE VENDOR WEBSITE COPY OR ONE-PAGER]
Use when: Someone asks for a project brief by end of day and you have 90 minutes and a head full of half-formed thoughts.
You are a senior business analyst. Turn the following raw notes into a structured project brief with these sections: Executive Summary (3 sentences max), Background, Proposed Approach, Key Risks (3 bullets), and Recommended Next Steps.
Tone: direct, no jargon, written for a senior audience.
Length: one page max.
Notes: [PASTE YOUR VOICE TRANSCRIPT]
Use when: You have 15 minutes before a meeting and materials to review. Need to walk in prepared.
I have a [type of meeting] in 15 minutes. Here are the materials: [paste]. My role is [your role]. Give me:
1. A 5-bullet summary of what I need to know
2. The two most important questions to ask
3. Any decisions that will likely be made, and what I should advocate for
4. One thing I should watch out for
Use when: A meeting just ended and you need to pull out decisions, action items, and unresolved questions before they evaporate.
Here's the transcript from a [meeting type] meeting. Give me:
1. Key decisions made
2. Action items with owners and deadlines
3. Open questions that weren't resolved
4. Anything that was agreed to that might be controversial or needs follow-up
Format as a clean summary I can share with attendees.
[Paste transcript]
Use when: You need to send a meeting recap email with action items but don't want to spend 20 minutes formatting it.
Based on this meeting summary, draft a follow-up email to all attendees. Include:
- A brief recap (3-4 sentences max)
- Action items formatted as a table: Who | What | By When
- Next meeting date and agenda topics
- Anything that needs a decision before then
Tone: professional but not stiff. Keep it under 200 words.
[Paste meeting notes]
Use when: You need AI help with a sensitive document but want to strip identifying details first. Copy this template before pasting anything confidential.
I'm going to share a [document type] with you. I've replaced all real names with placeholders (e.g., "Client A," "Employee 1"), removed specific financial figures, and stripped identifying details. Please help me [your task] based on the structure and content below.
[Paste sanitized content here]
Use when: You are stuck between options and your gut is not giving a clear answer.
I'm deciding between [options]. Help me build a decision matrix.
The factors that matter most to me are: [list them]
Ask me to rate each option on each factor, then calculate the weighted scores and tell me which option wins.
Use when: A process lives in someone's head and needs documentation a new hire could follow.
Here's how we currently do [PROCESS NAME]:
[PASTE CURRENT PROCESS DESCRIPTION OR NOTES]
Turn this into:
1. A numbered SOP (step-by-step instructions)
2. A checklist version (for quick reference)
3. A short "why this matters" paragraph for new hires
Use when: You feel busy but cannot explain where last week went.
I'll paste my meetings from last week below. For each meeting, categorize it as:
1. Essential (I was a key decision-maker or contributor)
2. Optional (I could have read the notes instead)
3. Wasteful (No clear outcome or my presence wasn't needed)
Calculate what percentage of my week fell into each category. Then suggest 3 specific meetings to decline or delegate next week.
[PASTE CALENDAR HERE]
I'm considering using AI to handle the following task: [DESCRIBE TASK].
Tell me:
1. What could go wrong that I might not catch immediately?
2. What input would make the output unreliable?
3. Should I supervise this closely, spot-check it, or trust it fully?
Be specific. No generic AI safety disclaimers.
Use when: An AI announcement lands and you need to know whether it changes anything in the next 90 days.
I just read this AI announcement: [paste headline or summary].
Act as a skeptical operations director at a mid-size company. Tell me:
1. Whether this requires any action in the next 90 days
2. What the realistic adoption timeline is for a non-technical team
3. What could go wrong during deployment
Keep your response under 150 words. No hype.
Use when: Before a vendor call, when you need to know how stable the company behind the tool is.
I'm evaluating [vendor name] for [use case]. Summarize any recent news about their financial performance, customer churn reports, or analyst concerns from the last six months. Then list three questions I should ask on a vendor call to pressure-test their ROI claims.