Claude Prompts for Personal Productivity

Take a book you just finished and distill it into exactly 3 actions you'll take in the next 30 days — not a summary, not a takeaway list.

Run a structured pre-mortem on a plan you are about to commit to. Surface failure modes, weight likelihood and impact, then propose specific mitigations.

Explore a decision by branching into multiple reasoning paths, scoring each branch on the same criteria, then committing to the strongest one with explicit trade-offs.

Generate a short, kind decline to a vendor or recruiter cold email — with an optional referral if appropriate, and zero guilt or hedge.

Force yourself to explain a concept simply, then have Claude poke holes in your explanation to find what you don't actually understand.

Take a yes/no decision and expand it into 4-6 real options with tradeoffs — because most binary decisions are false binaries.

Generate a complete email reply that answers every question in the original message and matches the sender's level of formality.

Compress a 20-message email chain into a structured summary: decisions made, open questions, who owes what, and the current state of play.

Sort a backlog of emails into respond-now, schedule, delegate, and archive buckets so you can clear the queue in one focused session.

Explain something complex by stripping it down to plain language, then surfacing the spots where the explanation gets thin so the learner can dig deeper.

Strip a problem down to its load-bearing assumptions, then rebuild from atoms. Forces Claude to separate what is true from what is convention.

Place protected focus blocks into a real calendar based on your energy peaks, deliverables, and existing meeting load — not generic 'block 2 hours daily' advice.

Take a messy stream of ideas, fragments, and half-thoughts and group them into themes with suggested next steps for each.

Build a custom inbox-zero workflow with filters, folders, recurring time blocks, and decline policies tailored to your role and email volume.

Invert the goal. Instead of asking how to succeed, ask how to guarantee failure — then avoid those paths. Forces Claude to map the failure surface, not just the success path.

Create a structured 30/60/90-day roadmap for learning a new domain or skill — with concrete resources, projects, and checkpoints.

Decompose a problem into Mutually Exclusive, Collectively Exhaustive buckets so analysis cannot double-count or quietly skip a branch.

Generate a polite, specific decline to a meeting that doesn't need you — with options to offer async input, a delegate, or a reschedule.

Turn messy meeting notes — half-sentences, side conversations, half-decisions — into a clean structured summary with decisions, actions, and open questions.

Turn a vague calendar invite and a few notes into a 1-page brief: goal, attendees, key questions, your stance, and the win condition.

Prepare 3-5 sharp, specific questions for a mentor, skip-level, or coffee chat — questions only this person could uniquely help you with.

Imagine the decision failed catastrophically 12 months from now and work backward to identify the failure modes you can prevent today.

Turn your scattered project notes into a clean status update for a manager or peer — calibrated to their preferred format and altitude.

Take raw highlights and notes from an article, book, or paper and turn them into a compact personal reference you'll actually re-read.

Determine whether a decision is reversible (Type 2 — make it fast) or irreversible (Type 1 — slow down) so you spend the right amount of deliberation.

Map the chain of consequences from a proposed action — not just what happens, but what happens because of what happens. Surface incentive shifts, downstream behaviors, and second-order risks.

Teach a topic by asking the learner questions that surface their actual model, then correcting only when the model breaks.

Get advice on a tough decision from a simulated 'personal board' — distinct advisors who'd give you genuinely different perspectives, not consensus.

Review your past or upcoming week's calendar and surface time leaks — meetings that should be async, recurring blocks losing value, and missing focus time.

Produce a personal weekly review covering what worked, what didn't, learnings, and the 3 priorities for next week — from your own raw input.