Prompts you can paste in right now

Everything on your plate, sorted into what actually matters this morning.

Organize my day for me.

Start by asking me to dump everything on my plate: tasks, deadlines, worries, half-finished ideas, in any order, as messy as it comes. Wait for my answer before organizing anything.

Then, using ONLY what I gave you:

Produce:
1. The top 3 things to do today, in order, with one line on why each earns its spot.
2. Quick wins: anything on the list that takes under 10 minutes.
3. What can wait until later this week without hurting me.
4. Anything I should hand off or say no to, and a one-line script for saying it.

Rules:
- Do not invent tasks I did not mention.
- If two things conflict, ask me which matters more instead of guessing.
- Keep the whole answer short enough to read in one minute.

A 20-page document becomes five bullets and a list of what they want from you.

Summarize a document for me, for someone walking into a meeting about it in 10 minutes.

Start by asking me to paste the full text of the document or email thread, and to tell you what the meeting is about. Wait for both before summarizing.

Then:

Produce:
1. A five-bullet summary of what it says.
2. Anything it asks of me: decisions, approvals, replies, money.
3. Every date and deadline mentioned.
4. Three smart questions I could ask in the meeting.

Rules:
- Use only what is in the text. If something important seems missing, say so.
- Plain English. No jargon from the document unless you explain it.
- Do not soften bad news. If the document contains a problem, lead with it.

Describe a task once, get a repeatable checklist you can hand to anyone.

Turn a task i do all the time into a checklist someone else could follow without calling me.

Start by asking me to describe the task in my own words, with my rough steps in any order. Tell me not to tidy it up first. Wait for my answer before building anything.

Then:

Produce:
1. A numbered checklist, one action per step, in the right order.
2. A short "before you start" list of anything to gather or set up first.
3. The 2 or 3 mistakes a first-timer is most likely to make, and how to avoid them.

Rules:
- Ask me about any step that seems to be missing rather than inventing it.
- Each step starts with a verb and fits on one line.
- Keep my judgment calls as judgment calls: flag them, do not decide them for me.

The project you keep avoiding, reduced to three 15-minute moves.

Help me get moving on a project i am stuck on.

Start by asking me two things: what the project is, and what has actually kept me from starting it. Wait for my answer before advising anything.

Then:

Produce:
1. The first three concrete steps, each doable in 15 minutes or less.
2. The one step to do right now, before anything else, and why that one.
3. What I can safely ignore until the first steps are done.

Rules:
- Steps must be physical actions I can do today, not advice like "get organized."
- If the real blocker sounds like a decision I have not made, name that decision plainly and give me the two most sensible options.
- No pep talk. Just the steps.

Messy notes in, a short professional email out.

Write a short, professional email from me to my client.

Start by asking me for my rough notes: who the email is to, what it needs to say, and any dates or numbers that belong in it. Rough is fine, in any order. Wait for my answer before writing anything.

Then, using ONLY the details I gave you:

Produce:
1. A subject line under 8 words.
2. The email: under 150 words, warm and plain English, no jargon.
3. A one-line text-message version of the same update.

Rules:
- Use only the facts I gave you. If something important is missing, ask me for it instead of inventing it.
- No filler like "I hope this email finds you well." Start with the point.
- Friendly and direct, like a note from someone who respects my time.

Bad news delivered so the relationship survives the email.

Help me deliver a hard message honestly, without burning the relationship.

Start by asking me: what happened, who the message is going to, and what I need from them. Ask me to paste my draft too, or the rough angry version, if I have one. Wait for my answer before rewriting anything.

Then:

Produce:
1. A rewrite that is calm, direct, and takes responsibility where I actually have it.
2. A softer version, in case I decide the first one is too blunt.
3. A short list of phrases to avoid in this situation, pulled from my draft if any appear there.

Rules:
- Do not hide the point in politeness. The reader must know exactly what happened and what happens next.
- No fake apologies and no over-apologizing. One sincere acknowledgment is enough.
- Keep it under 150 words.

A public reply that wins the next customer, even if this one is gone.

Write my response to a customer review. remember that future customers read these replies more carefully than the review itself.

Start by asking me to paste the review, and to tell you what actually happened from my side. Wait for both before drafting.

Then:

Produce:
1. A public reply: professional, specific, under 100 words, no arguing.
2. A short private message to the customer, if reaching out directly makes sense here.
3. One sentence on what, if anything, is worth changing in how we work so this does not repeat.

Rules:
- Never blame the customer in the public reply, even if they are wrong.
- Do not admit fault for things that did not happen. Correct false claims calmly, with facts.
- No corporate phrases like "we take this very seriously." Write like a real owner.

The thing you explain ten times a week, in words anyone gets the first time.

Help me explain something so a busy non-expert gets it on the first read.

Start by asking me what needs explaining, and who is asking: a customer, a client, my kid, someone on my crew. Who it is changes the answer. Wait for both before explaining.

Then:

Produce:
1. A three-sentence plain-English explanation.
2. One everyday comparison that makes it click, drawn from normal life, not my industry.
3. The three questions people usually ask next, each answered in a sentence.

Rules:
- No jargon at all. If a technical word is unavoidable, define it in the same sentence.
- Do not oversimplify to the point of being wrong. If precision matters somewhere, keep it and say why.
- Friendly, not condescending. The reader is smart, just busy.

The pros, cons, and hidden costs you would have found at 2am, delivered now.

Be my thinking partner on a decision. i decide; you make sure i see clearly.

Start by asking me three things, one at a time: what the decision is, what options I am weighing, and what matters most to me in the outcome. Wait for all three before weighing in.

Then:

Produce:
1. The honest pros and cons of each option, including the ones I probably do not want to hear.
2. Hidden costs or second-order effects of each option that people usually miss.
3. The two or three questions I should answer before choosing.
4. Your read on which option fits what I said matters most, with your reasoning shown.

Rules:
- Challenge my framing if the options I listed are not the real choice.
- No hedging on every line. Take positions and show why.
- If this decision is easily reversible, say so. That changes how much analysis it deserves.

Walk into the conversation knowing what to ask and what should worry you.

Prepare me to evaluate vendors for something i am hiring out, like someone who has bought it many times.

Start by asking me what the job or service is, and what my budget or constraints are. If I do not know the budget, say so and work from the job alone. Wait for my answer before preparing anything.

Then:

Produce:
1. The 8 to 10 questions worth asking, ordered by how much the answer matters.
2. Red flags: answers or behaviors that should end the conversation.
3. What a fair price structure usually looks like for this kind of work, and the pricing tricks to watch for.
4. One thing buyers usually forget to nail down in writing.

Rules:
- Questions must be specific to this job, not generic "tell me about your experience" filler.
- If my budget looks unrealistic for what I described, say so plainly.
- General guidance only: you do not know my local market, so tell me where local rates vary.

Know what you are agreeing to before you sign, not after.

Translate a contract or quote into plain english for the person about to sign it. this is a first read, not legal advice; anything that will be signed still goes past a professional.

Start by asking me to paste the full text, and to tell you which side of it I am on: am I signing, or am I the one offering it. Wait for both before translating.

Then:

Produce:
1. What I am agreeing to, in one short paragraph.
2. Every obligation this puts on me: payments, deadlines, renewals, cancellation terms.
3. The clauses that favor the other side, ranked by how much they could cost me.
4. The questions to ask, or the changes to request, before signing.

Rules:
- Quote the exact line from the document when you flag something.
- Do not invent standard terms that are not in this text.
- If a clause is genuinely unusual for this kind of agreement, say so and explain why it stands out.

Twenty minutes from "never heard of it" to holding your own in the conversation.

Teach me something in 20 minutes of reading, aimed at exactly what i need it for.

Start by asking me three things, one at a time: the topic or tool, what I already know about it, and what I actually need to do with it. That last one decides everything you teach me, so do not skip it. Wait for all three before teaching.

Then:

Produce:
1. The five ideas that matter most, one short paragraph each, in the order I should learn them.
2. The vocabulary I will hear, each term defined in one line.
3. A first exercise I can do today to make it stick.
4. The one beginner mistake that costs people the most.

Rules:
- Skip the history lesson unless it changes what I should do.
- Tie every idea back to what I said I need it for.
- End by asking me one question that tests whether I actually got it.