Free AI Prompt Templates for Productivity (2026): 15 Ready-to-Use Prompts

The difference between a bad AI prompt and a good one isn’t creativity.

It’s specificity.

“Write me a professional email” gets you something generic. “Write a 150-word email declining a vendor meeting, polite but firm, signed as a busy founder” gets you something you can actually send.

That gap is the whole game. And most people are stuck on the wrong side of it.

Over the past two years I’ve run dozens of AI workshops in Austin. The single most common thing I see: people fire off a vague request, get back something mediocre, and then either blame themselves or blame the AI. Meanwhile, the people who’ve learned to write tightly scoped prompts are getting first drafts they can use in 30 seconds.

This page gives you 15 ready-to-use prompts across six categories. Copy them. Customize them. Save them. That’s it.

But first, let me show you the formula that makes all of them work.

The Prompt Formula I Use for Everything

I call it OCE. Every prompt I write hits three things:

• Outcome — what artifact do I actually want?
• Context — what does the AI need to know to get it right?
• Expectations — format, length, tone, constraints

Most people write prompts that only cover the outcome. “Summarize this.” “Draft an email.” That’s one-third of a prompt. The AI guesses on context and expectations, and the output reflects that.

Here’s an example of the gap:

Weak prompt:

“Write a follow-up email after a sales call.”

OCE prompt:

“Write a follow-up email after a 30-minute sales discovery call. The prospect runs a 10-person marketing agency, showed interest in our CRM tool but raised a budget concern. Tone: warm and confident. Length: under 150 words. End with a soft next step — offer to send a case study, not a hard ask.”

Same task. Completely different output.

The more clearly you define the outcome, context, and expectations, the less editing you do. That’s what saves you time.

15 Ready-to-Use Productivity Prompts

Email

Prompt 1: Draft a reply to a difficult email

You're helping me respond to a difficult email professionally. Here's the email I received: {paste email}. My goal: acknowledge their concern, explain my position briefly, and keep the relationship intact. Tone: calm and direct. Length: 100-150 words. Do not be apologetic for things that weren't my fault.

Prompt 2: Summarize a long email thread

Summarize this email thread for me. I need: (1) the core issue being discussed, (2) any decisions made, (3) what's still unresolved, (4) any action items I own. Output as a bulleted list. Thread: {paste thread}

Prompt 3: Write a professional decline

Write a polite but clear decline to this request: {describe request}. I want to preserve the relationship and leave the door open for the future. Do not over-explain. Under 100 words.

Meeting Prep

Prompt 4: Pre-call research brief

I have a 30-minute call with {name/company} on {date}. Their company does {brief description}. Based on what you know about them, give me: (1) 3 things worth knowing before the call, (2) 2 questions I should ask, (3) one potential objection and how to address it. Format: short bullets.

Prompt 5: Meeting agenda

Create a focused agenda for a {length}-minute meeting. Goal of the meeting: {describe goal}. Attendees: {list roles}. I want time blocked for: context-setting, discussion, and clear next steps. Output as a formatted agenda with time blocks.

Writing

Prompt 6: First draft from bullet points

Turn these bullet points into a well-written first draft. Tone: {professional/casual/friendly}. Audience: {describe reader}. Length: approximately [X] words. Preserve all key ideas but make it flow naturally. Bullet points: {paste list}

Prompt 7: Edit for clarity

Edit this paragraph for clarity. Make it shorter, more direct, and easier to read. Remove any filler phrases. Keep my voice — don't make it sound formal or robotic. Return just the revised paragraph. {paste paragraph}

Prompt 8: Executive summary

Write a 150-word executive summary of this document. Include: the core problem, the proposed solution, and the expected outcome. Audience: senior leadership who won't read the full document. {paste document or key sections}

Planning

Prompt 9: Weekly priority list

It's Monday morning. Here are my open tasks and projects: {paste list}. Help me pick my top 5 priorities for this week. Consider: deadlines, impact, what's been sitting too long. Output as a ranked list with one sentence explaining each pick.

Prompt 10: Project breakdown

I need to break this project into manageable steps: {describe project}. Give me a week-by-week plan assuming I have {X hours/week} to work on it. Flag any dependencies or decisions I need to make early. Output as a simple numbered list.

Prompt 11: Goal decomposition

I want to achieve this goal in 90 days: {describe goal}. Break it into three monthly milestones. For the first month, give me a specific week-by-week plan. Be concrete — avoid vague actions like "work on X." Tell me exactly what done looks like.

Learning

Prompt 12: Explain a concept simply

Explain {concept} to me like I'm smart but new to this topic. Use one analogy and one real-world example. Skip the jargon. Under 200 words.

Prompt 13: Create a study guide from notes

Here are my raw notes on {topic}: {paste notes}. Turn them into a study guide with: (1) key concepts defined in one sentence each, (2) the 3-5 most important ideas to remember, (3) 5 quiz questions I could use to test myself. Format: clean sections with headers.

Problem Solving

Prompt 14: Devil’s advocate review

I'm about to make this decision: {describe decision}. Play devil's advocate. Give me the three strongest arguments against it, the assumptions I might be wrong about, and one thing I may not have considered. Be direct — I'm not looking for validation.

Prompt 15: Decision framework

Help me think through this decision: {describe situation}. I'm considering: Option A: {describe} vs Option B: {describe}. For each option, give me: the upside, the downside, and the biggest risk. Then give me a recommendation based on what I've told you, with your reasoning.

How to Save and Reuse These Prompts

Writing a good prompt once and retyping it from memory every time is exactly the wrong way to use it.

Here are three tools worth considering:

TextExpander — I’ve been using TextExpander for years, originally for email snippets. It works the same way for AI prompts. Store a prompt under a shortcode like ;weeklyplan, type it anywhere (ChatGPT, Claude, Notion), and it expands instantly. Works across all AI tools. The team plan means everyone on your team uses the same prompt library, which is actually huge for consistency.

Check TextExpander pricing here.

Claude Projects — If you use Claude Pro, Projects is underrated for this. Create a project called “Weekly Planning” or “Email Drafts,” paste your go-to prompts into the project instructions, and they’re available every time you open that project. Great for context that stays constant — your company background, your tone preferences, your common task types.

ChatGPT Custom Instructions — Not as flexible as Projects, but free. Go to Settings → Personalization → Custom Instructions and set your default context once. Every new chat inherits it. Things like your job title, writing style, preferred output format. Takes five minutes to set up and saves you from re-explaining yourself every session.

Pick one. Start there.

How to Upgrade Any Mediocre Prompt

You already have the OCE formula. Here’s a faster way to diagnose why a prompt isn’t working:

Ask yourself three questions:

1. Did I define the artifact clearly? (Not “help me with email” — “write a 100-word reply”)
2. Did I give it the context it can’t assume? (Who’s the audience, what’s the situation)
3. Did I set any constraints? (Length, tone, format, what to avoid)

If you can’t answer yes to all three, the prompt is incomplete.

One thing I started doing at my workshops: I have people read their first prompt out loud and identify what they assumed the AI would figure out. Nine times out of ten, that’s exactly where the output fell short.

The one-line diagnostic: If your output could have come from anyone’s prompt, your context was too thin.

Quick fixes that work almost every time:

• Add a word count limit (“under 150 words”) — forces the AI to prioritize
• Add “do not include [X]” — telling it what to leave out is often more useful than adding more instructions
• Add a reader description (“my audience is non-technical executives”) — completely changes tone without changing the task
• Ask for a specific format (“output as a numbered list” or “output as a table with three columns”)

Small changes. Big difference in output quality.

FAQ

Do these prompts work on Claude, ChatGPT, and Gemini?

Yes. The OCE structure works across all three. Claude tends to follow complex formatting instructions more precisely. ChatGPT handles casual tone well. Gemini is solid for research and summarization tasks. Pick your preferred tool and the prompts above should work with minor adjustments.

Should I use the same prompt every time or customize it?

Customize the context section each time — that’s the part that’s specific to your situation. The structure (outcome + context + expectations) stays the same. Think of it like a template where you fill in the blanks rather than rewriting from scratch.

What’s the fastest way to improve my prompting?

Pick one task you do every week — weekly planning, email drafts, whatever. Write a single good prompt for it using OCE. Save it in TextExpander or Claude Projects. Use it five times. You’ll know after five uses what to tweak. Trying to optimize every prompt at once doesn’t work — the iteration loop is too long. One prompt, one week, repeat.

What’s Next

If you want to go deeper on using AI for productivity — not just prompts, but full workflows and automation — check out the Asian Efficiency AI workshops. We run small group sessions in Austin, plus remote options. Last one sold out in 48 hours.

You can also subscribe to The Productivity Show — we cover practical AI topics regularly, usually with real examples from the workshop room.

The prompts above are a solid starting point. But the real leverage is building systems around them, so they run without you having to think about it every time.

Start with one. See what happens.