Claude Prompt Library

Reclaim Your Time and Focus with Claude AI

35 copy-paste prompts

35 analytical Claude prompts for time management, task prioritization, meeting optimization, decision-making frameworks, goal setting, and deep work systems — built for Claude's structured thinking.

Time Management

5 prompts

Weekly Time Audit

1/35

<context> Role: [YOUR JOB TITLE] Typical work hours: [START-END] Current time breakdown estimate: - Meetings: [HOURS/WEEK] - Email/messages: [HOURS/WEEK] - Deep work: [HOURS/WEEK] - Admin tasks: [HOURS/WEEK] - Other: [DESCRIBE] Biggest time complaint: [WHAT FRUSTRATES YOU] Most important work: [WHAT ACTUALLY MOVES THE NEEDLE] </context> <task> Conduct a weekly time audit: 1. Time categorization: sort my activities into 4 buckets: - High-value creation (directly produces important outcomes) - Necessary coordination (meetings, communication that enables work) - Administrative overhead (reports, updates, scheduling) - Time waste (could be eliminated, delegated, or automated) 2. ROI analysis: for each activity, estimate the value-per-hour 3. The 80/20 diagnosis: which 20% of my activities produce 80% of my results? 4. Time reclamation plan: identify 5-8 hours per week to reclaim and how 5. Ideal week template: redesign my week allocating time by priority, not by habit 6. Energy mapping: align high-value work with high-energy times, low-value with low-energy 7. Protection plan: specific strategies to defend high-value time blocks from interruption Be honest — most knowledge workers spend less than 3 hours per day on truly high-value work. </task>

Audits your weekly time usage to identify waste, protect high-value work, and redesign the week around results.

💡

Pro tip: Track your actual time for one week before running this audit. Your estimates of how you spend time are almost certainly wrong. Use a simple timer app and log every activity.

Daily Planning System

2/35

<context> Role: [DESCRIBE] Daily tasks: [LIST TODAY'S TASKS] Meetings today: [LIST WITH TIMES] Deadlines: [ANY APPROACHING DEADLINES] Energy level today: [HIGH / MEDIUM / LOW] Yesterday's unfinished items: [LIST] Most important project right now: [DESCRIBE] </context> <task> Plan my day: 1. Priority ranking: sort all tasks using the Eisenhower matrix (urgent+important, important not urgent, urgent not important, neither) 2. MIT (Most Important Task): identify the ONE task that, if completed, makes today successful 3. Time-blocked schedule: assign every task to a specific time block considering: - My energy level and when I am most focused - Meeting gaps and available deep work windows - Task difficulty and cognitive demand 4. Buffer time: build in 30-60 minutes for unexpected interruptions 5. Batch processing: group similar tasks together (all emails in one block, all calls in another) 6. Not-today list: tasks to explicitly defer to tomorrow with reasoning 7. End-of-day review questions: 3 questions to answer before closing work for the day A good plan prevents the reactive spiral of doing whatever is loudest instead of what matters most. </task>

Creates a time-blocked daily plan with MIT identification, energy-aligned scheduling, and explicit deferrals.

💡

Pro tip: Plan tomorrow's MIT the night before. When you wake up knowing exactly what your most important task is, you eliminate the dangerous 30-minute "what should I work on?" decision lag that leads to email checking.

Meeting Time Reducer

3/35

<context> Current weekly meetings: [LIST EACH — name, duration, frequency, attendees, your role] Total meeting hours per week: [COUNT] Meetings I run: [WHICH ONES] Meetings I attend but do not run: [WHICH ONES] How I feel about my meeting load: [DESCRIBE] </context> <task> Reduce my meeting burden: 1. Meeting audit: for each meeting, rate it: - Necessity (1-10): does this need to exist as a meeting? - My necessity (1-10): do I specifically need to attend? - Efficiency (1-10): is the meeting well-run? 2. Elimination candidates: meetings that could be an email, Slack thread, or async update 3. Reduction candidates: meetings that should be 15 minutes instead of 30 or 30 instead of 60 4. Delegation candidates: meetings where I can send a delegate or get notes afterward 5. Frequency changes: weekly meetings that should be biweekly or monthly 6. Format changes: standing meetings, walking meetings, or async-first approaches 7. Scripts: exact language to use when declining, shortening, or changing meetings 8. Target: calculate my new meeting hours per week after implementing these changes Every hour in a meeting is an hour not spent on the work the meeting is about. </task>

Audits and reduces meeting load with elimination, reduction, and delegation recommendations plus decline scripts.

💡

Pro tip: Start by declining one meeting this week. The meeting you were afraid to decline almost never causes problems. This builds confidence to decline more.

Procrastination Buster

4/35

<context> Task I am procrastinating on: [DESCRIBE] Why it matters: [CONSEQUENCES OF NOT DOING IT] How long I have been avoiding it: [DURATION] What I do instead: [DESCRIBE AVOIDANCE BEHAVIORS] The feeling when I think about the task: [DESCRIBE — anxiety, boredom, overwhelm, confusion, perfectionism] Past tasks I procrastinated on: [PATTERNS] </context> <task> Diagnose and break through this procrastination: 1. Root cause identification: which procrastination type is this? - Fear of failure (perfectionism) - Task ambiguity (do not know where to start) - Emotional avoidance (the task triggers discomfort) - Decision fatigue (too many choices within the task) - Lack of meaning (the task feels pointless) 2. Specific intervention for my root cause 3. Break it down: split the task into steps so small that the first one takes under 5 minutes 4. Commitment device: a specific constraint that makes starting easier than avoiding 5. Environment design: how to set up my space to make starting automatic 6. The 2-minute start: the exact first physical action to take right now 7. Reward structure: what I earn after completing each milestone 8. Accountability: who to tell and what commitment to make Procrastination is not laziness. It is emotion management. Address the emotion and the action follows. </task>

Diagnoses the root cause of procrastination and provides a targeted intervention with micro-steps and commitment devices.

💡

Pro tip: The hardest part is the first 2 minutes. Commit to working for just 2 minutes — you can stop after that. You almost never will, because starting is the actual barrier, not doing.

Email Management System

5/35

<context> Daily email volume: [NUMBER OF EMAILS] Time spent on email: [HOURS PER DAY] Email response expectations: [HOW FAST DO PEOPLE EXPECT REPLIES] Types of emails: [LIST — requests, updates, newsletters, etc.] Current email habits: [DESCRIBE — check constantly, inbox zero, chaos, etc.] Biggest email frustration: [DESCRIBE] </context> <task> Design an email management system: 1. Processing schedule: specific times to check email and how long per session 2. Triage system: a decision tree for every email (respond now, schedule, delegate, archive, delete) 3. The 2-minute rule: if it takes less than 2 minutes, respond immediately; if not, schedule it 4. Template library: identify 5-10 email types I send repeatedly and write templates for each 5. Folder/label structure: a minimal organization system (not a complex taxonomy) 6. Notification settings: what to turn off and what to keep 7. Unsubscribe sprint: how to reduce incoming volume by 30-50% 8. Auto-responder strategy: when and how to set expectations about response time 9. Email to task conversion: how to turn email action items into my task system without losing them 10. Inbox zero method: a daily routine for reaching zero that takes 30 minutes or less Email should serve your priorities, not dictate them. </task>

Creates a complete email management system with processing schedules, triage decisions, and templates for common responses.

💡

Pro tip: Check email 3 times per day: morning, after lunch, and before end of day. Between checks, close your email completely. The constant checking is what makes email overwhelming, not the volume.

XML tags are just the start. Learn the full Claude workflow.

A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.

Start 14-Day Free Trial

Task Prioritization

5 prompts

Task Prioritization Matrix

6/35

<context> All current tasks and projects: [LIST EVERYTHING ON YOUR PLATE — work, personal, side projects] Deadlines: [LIST ANY WITH DATES] Stakeholder expectations: [WHO IS WAITING ON WHAT] Your goals this quarter: [LIST] Resources available: [TIME, ENERGY, BUDGET, HELP] </context> <task> Prioritize my entire task list: 1. Categorize using ICE framework (Impact × Confidence × Ease, scored 1-10 each) 2. Map onto Eisenhower matrix: urgent/important grid 3. Dependencies: identify tasks that block other tasks (do these first) 4. Identify the 3 tasks that, if completed, would make everything else easier 5. Identify tasks to: - Do immediately (high impact, time-sensitive) - Schedule (high impact, not urgent) - Delegate (someone else can do this) - Eliminate (low impact, should not be on the list at all) 6. Create a priority-ordered action list for the next 5 work days 7. The "stop doing" list: tasks I should remove from my plate entirely with suggested communication Having a lot to do is not the problem. Not knowing what matters most is the problem. </task>

Prioritizes your entire task list using ICE scoring, dependency mapping, and creates a daily action plan with a stop-doing list.

💡

Pro tip: The "stop doing" list is more powerful than the "to do" list. Every task you eliminate frees time and mental energy for what actually matters. Be ruthless.

Project Decomposer

7/35

<context> Project: [DESCRIBE THE PROJECT] Deadline: [WHEN] Current state: [NOT STARTED / IN PROGRESS / STUCK] Resources: [WHO IS WORKING ON THIS, TOOLS AVAILABLE] Blockers: [WHAT IS PREVENTING PROGRESS] Definition of done: [WHAT DOES COMPLETION LOOK LIKE] </context> <task> Decompose this project into manageable pieces: 1. Work breakdown: split the project into phases, then tasks, then sub-tasks 2. For each task: estimated time, owner, dependencies, and deliverable 3. Critical path: the sequence of tasks that determines the timeline (any delay here delays everything) 4. Parallel work: which tasks can happen simultaneously 5. Milestone markers: 4-6 checkpoints to verify progress 6. Risk register: what could go wrong at each phase and mitigation plans 7. First action: the single next physical action to take right now to start momentum 8. Weekly schedule: tasks mapped to specific weeks between now and deadline Large projects paralyze because they are overwhelming as a whole. Break them into tasks small enough that each one feels achievable. </task>

Decomposes a large project into phases, tasks, and sub-tasks with critical path, risks, and a weekly execution schedule.

💡

Pro tip: The critical path determines your real deadline. If you focus on tasks that are not on the critical path, you feel productive but do not actually move the project forward.

Weekly Review Framework

8/35

<context> This week's planned tasks: [WHAT I INTENDED TO DO] Actual accomplishments: [WHAT I ACTUALLY DID] Unfinished tasks: [WHAT CARRIED OVER] Unexpected tasks: [WHAT APPEARED THAT WAS NOT PLANNED] Energy level this week: [1-10] Key meetings or events: [NOTABLE MOMENTS] </context> <task> Conduct a structured weekly review: 1. Completion audit: what percentage of planned tasks did I finish? What caused the gap? 2. Win identification: top 3 accomplishments this week (celebrate them) 3. Learning extraction: what did I learn about my productivity, priorities, or work patterns? 4. Unfinished business: for each incomplete task — carry forward, delegate, or drop? 5. Interruption analysis: what unplanned work consumed my time? Was it worth it? 6. Next week planning: - Top 3 priorities for next week - Meetings to accept, decline, or shorten - Time blocks to protect for deep work - One habit or system to improve 7. Monthly goal check: am I on track for my monthly and quarterly goals? 8. One adjustment: the single change that would make next week better than this week Review weekly. Adjust monthly. Transform quarterly. </task>

Structures a productive weekly review with completion analysis, learning extraction, and next-week planning.

💡

Pro tip: Schedule the weekly review at the same time every week (Friday afternoon works well). Make it a non-negotiable appointment with yourself. The 30 minutes invested saves hours of directionless work next week.

Delegation Decision Framework

9/35

<context> Tasks I am currently doing: [LIST] Team members available: [LIST WITH SKILLS] Tasks I think I should delegate: [LIST] Why I have not delegated yet: [HONEST REASONS — trust, speed, quality, guilt, etc.] </context> <task> Create a delegation framework: 1. Delegation audit: for each task, score on: - Must I specifically do this? (yes/no) - Would delegating free significant time? (yes/no) - Can someone else do this at 80%+ of my quality? (yes/no) - Is this a growth opportunity for someone? (yes/no) 2. Delegation priority list: tasks to delegate ordered by time-reclaimed 3. For each delegation: - Who should do it and why - What "done" looks like (quality standard) - How to hand off without micromanaging - Check-in schedule (not hovering, not disappearing) 4. Resistance analysis: address my specific reasons for not delegating and reframe them 5. Communication templates: how to delegate with clarity and respect 6. Time reinvestment plan: specifically what I will do with the reclaimed time Delegation is not about dumping work. It is about putting work with the right person. </task>

Creates a systematic delegation framework with task scoring, handoff instructions, and resistance reframing.

💡

Pro tip: If someone can do the task at 70% of your quality, delegate it. Your 30% quality premium is not worth the time it costs you. Reserve your time for the tasks only you can do.

Decision Fatigue Reducer

10/35

<context> Decisions I make daily: [LIST — from trivial to important] Decisions I struggle with: [WHICH ONES TAKE THE MOST ENERGY] Decision-making style: [QUICK / ANALYTICAL / INDECISIVE / VARIES] Areas where I overthink: [DESCRIBE] Time wasted on low-stakes decisions: [ESTIMATE] </context> <task> Reduce my decision fatigue: 1. Decision audit: categorize all decisions as high-stakes (irreversible, significant impact) or low-stakes (reversible, minor impact) 2. Low-stakes elimination: create rules, defaults, and automations that remove these decisions entirely - Meal defaults - Clothing defaults - Meeting response defaults - Communication defaults 3. Decision templates: for recurring decisions, create a standard framework so I think once, not every time 4. Time-boxing: for medium-stakes decisions, set a maximum deliberation time 5. Two-way door test: identify decisions that are easily reversible (just decide quickly and adjust) 6. High-stakes protocol: a structured process for the few decisions that actually deserve deep analysis 7. Daily decision budget: protect my best decision-making energy for what matters most The goal is not to make perfect decisions. It is to make the right decisions quickly and the unimportant ones automatically. </task>

Eliminates low-stakes decisions through defaults and rules, and structures high-stakes decisions for better outcomes.

💡

Pro tip: Jeff Bezos uses the "two-way door" framework: if a decision is easily reversible, decide fast and move on. Only slow down for irreversible, high-impact decisions. Most decisions are two-way doors.

Deep Work & Focus

5 prompts

Deep Work System Design

11/35

<context> Work type: [DESCRIBE YOUR MOST IMPORTANT COGNITIVELY DEMANDING WORK] Current deep work hours per week: [ESTIMATE] Biggest distractions: [LIST] Work environment: [OFFICE / HOME / HYBRID / OPEN PLAN] Schedule flexibility: [HIGH / MODERATE / LOW] Family/team demands: [DESCRIBE OBLIGATIONS THAT INTERRUPT] </context> <task> Design a deep work system: 1. Deep work audit: how many hours of undistracted, cognitively demanding work do I actually do now? 2. Target: based on my role and work type, how many deep work hours do I need per week? 3. Schedule architecture: design specific deep work blocks into my week - Best times for deep work based on my energy and obligations - Block duration: 90-minute or 2-hour blocks with rationale - Ritual: specific start and end routines for each block 4. Distraction elimination: - Digital: phone, notifications, email, Slack — specific settings - Physical: door sign, headphones, location change - Social: how to communicate deep work blocks to colleagues and family 5. Environment optimization: what the ideal deep work environment looks like for me 6. Metrics: how to track deep work hours and the output they produce 7. Gradual build: a 4-week plan to increase deep work hours progressively Deep work is the superpower of the knowledge economy. Protect it like your most valuable asset. </task>

Designs a complete deep work system with schedule blocks, distraction elimination, environment optimization, and a 4-week build plan.

💡

Pro tip: Start with one 90-minute deep work block per day. Protect it fiercely. As it becomes habit, add a second block. Most people cannot sustain more than 4 hours of true deep work per day.

Focus Environment Optimizer

12/35

<context> Where I work: [DESCRIBE PHYSICAL SPACE] Digital tools I use: [LIST APPS AND TOOLS] Noise situation: [QUIET / NOISY / VARIABLE] Current focus aids: [MUSIC / WHITE NOISE / NOTHING / etc.] Biggest focus killers: [LIST TOP 5] Focus duration before distraction: [MINUTES] </context> <task> Optimize my focus environment: 1. Physical space audit: what helps and hurts focus in my current setup 2. Digital environment: - App-by-app notification audit: what to mute, schedule, or disable - Browser setup: extensions to block distractions, focused homepage - Phone: Do Not Disturb schedules, app removal, grayscale mode 3. Audio environment: evidence-based recommendations for my work type (silence vs music vs noise) 4. Visual environment: desk organization, screen setup, line of sight 5. Sensory optimization: lighting, temperature, air quality, ergonomics 6. Focus ritual: a 3-minute sequence that signals "deep work mode" to my brain 7. Break protocol: when and how to take breaks that restore focus (not breaks that destroy it) 8. Emergency interruption protocol: how to handle truly urgent interruptions without losing flow Your environment shapes your behavior more than your willpower does. Design it for focus. </task>

Optimizes physical and digital environments for sustained focus with notification audits, rituals, and break protocols.

💡

Pro tip: The single most impactful change most people can make is putting their phone in another room during deep work. Not on silent — in another room. Out of sight removes the temptation entirely.

Attention Restoration Plan

13/35

<context> Current state: [BURNED OUT / SCATTERED / CONSTANTLY DISTRACTED / BRAIN FOG] Duration of attention problems: [DAYS / WEEKS / MONTHS] Sleep: [HOURS AND QUALITY] Exercise: [FREQUENCY] Screen time: [DAILY HOURS] Stress level: [1-10] Substances: [CAFFEINE / ALCOHOL / OTHER] </context> <task> Create an attention restoration plan: 1. Root cause assessment: what is most likely degrading my attention (sleep, stress, overstimulation, nutrition, or medical) 2. Digital detox protocol: a structured reduction in stimulation (not cold turkey — sustainable) 3. Sleep-attention connection: how to improve sleep specifically to improve focus 4. Physical restoration: exercise, nature exposure, and movement practices that restore cognitive function 5. Cognitive exercises: specific practices to rebuild attention span (progressive difficulty) 6. Information diet: reduce input volume (news, social media, notifications) to reduce cognitive load 7. Recovery timeline: what to expect at 1 week, 2 weeks, 1 month of following the plan 8. When to seek help: signs that attention problems may need medical evaluation (ADHD, thyroid, depression) Attention is a finite resource that degrades with overuse and restores with rest. Treat it like a physical muscle. </task>

Creates a multi-factor attention restoration plan addressing digital, physical, sleep, and cognitive contributors.

💡

Pro tip: Attention restoration starts with reducing inputs, not increasing effort. You cannot focus your way out of overstimulation. Reduce first, then rebuild.

Creative Block Breaker

14/35

<context> Creative work type: [WRITING / DESIGN / CODING / STRATEGY / PROBLEM-SOLVING / OTHER] What I am stuck on: [DESCRIBE THE SPECIFIC BLOCK] How long I have been stuck: [DURATION] What I have tried: [DESCRIBE ATTEMPTS] Deadline pressure: [NONE / MODERATE / HIGH] Recent creative output quality: [GOOD / DECLINING / POOR] </context> <task> Break through this creative block: 1. Block diagnosis: which type of block is this? - Blank page paralysis (cannot start) - Perfectionism block (nothing feels good enough) - Direction block (too many possibilities) - Burnout block (creatively depleted) - Fear block (afraid of judgment) 2. Immediate intervention: a specific exercise to do in the next 10 minutes 3. Constraint therapy: add specific limitations that paradoxically free creativity 4. Input refresher: new sources of inspiration to break the pattern 5. Process change: alter HOW you work (location, tools, medium, collaboration) 6. Quantity over quality sprint: produce 10 bad versions in 30 minutes to break the seal 7. Incubation strategy: productive ways to step away that let your subconscious work 8. Return protocol: how to come back to the work fresh after a break Creative blocks are almost never about creativity. They are about fear, perfectionism, or depletion. </task>

Diagnoses the type of creative block and provides targeted interventions from constraint therapy to quantity sprints.

💡

Pro tip: Lower your standards temporarily. Write a terrible first draft, design an ugly first mockup, code an embarrassing first version. The purpose of the first version is to exist, not to be good. Good comes from revision.

Single-Tasking Protocol

15/35

<context> Multitasking habits: [DESCRIBE — how many tabs, concurrent tasks, context switching] Work that suffers from multitasking: [DESCRIBE] Why I multitask: [HABIT / ANXIETY / BOREDOM / TOO MANY DEMANDS / FOMO] Tasks that genuinely need parallel attention: [LIST — if any] </context> <task> Design a single-tasking protocol: 1. Multitasking cost calculation: estimate how much time I lose daily to context switching (research says 40% of productive time) 2. Task sequencing: how to order tasks so each gets full attention in sequence 3. Environment setup: physical and digital changes that prevent unintentional multitasking 4. The "one tab" rule: specific implementation for digital work 5. Batch processing: group similar tasks together instead of interleaving different types 6. Interruption protocol: what to do when something "urgent" arrives during focused work 7. Transition ritual: a 2-minute routine between tasks that clears the previous task from working memory 8. Progress visibility: how to see momentum building on single tasks (not scattered across many) 9. 7-day challenge: a structured one-week experiment in single-tasking with daily adjustments The human brain does not multitask. It rapidly switches between tasks, losing efficiency with every switch. </task>

Creates a single-tasking protocol with environment design, batch processing, and a 7-day challenge to build the habit.

💡

Pro tip: Try single-tasking for just one day. Close all tabs except the one you are working on. Turn off notifications. Work on one thing at a time. You will be astonished at how much more you accomplish.

Goal Setting

5 prompts

Annual Goal Framework

16/35

<context> Areas of life: career, health, relationships, finances, personal growth, creative, other Last year's goals: [WHAT YOU SET AND HOW THEY WENT] Biggest achievement last year: [DESCRIBE] Biggest regret from last year: [WHAT YOU WISH YOU HAD DONE] Current life situation: [BRIEF OVERVIEW] Time and resources available for goals: [REALISTIC ASSESSMENT] </context> <task> Create an annual goal framework: 1. Life vision check: what does my ideal life look like in 3 years? (context for annual goals) 2. Goal selection: 3-5 goals maximum (not 10 — focus beats breadth) 3. For each goal: - SMART definition (specific, measurable, achievable, relevant, time-bound) - Why this goal matters to ME (not why it should matter) - The leading indicators (weekly actions) vs lagging indicators (outcome metrics) - Quarterly milestones - One keystone habit that drives progress daily - The obstacle I will definitely face and my plan for it 4. Anti-goals: 3 things I will NOT pursue this year (to protect focus) 5. Quarterly review schedule: 4 dates in my calendar for goal reviews 6. Accountability system: how I will stay on track when motivation fades 3-5 goals pursued with intensity beats 10 goals pursued with scattered attention. </task>

Creates a focused annual goal framework with quarterly milestones, keystone habits, obstacle planning, and anti-goals.

💡

Pro tip: Set fewer goals than you think you should. Achieving 3 out of 3 goals feels incredible. Achieving 3 out of 10 feels like failure even though the outcomes are identical. Fewer goals, more success.

OKR Builder

17/35

<context> Role: [YOUR ROLE] Organization goal: [COMPANY OR TEAM OBJECTIVE IF RELEVANT] Time period: [QUARTER] Current projects: [LIST MAJOR INITIATIVES] Team: [SIZE AND ROLES IF MANAGING OTHERS] </context> <task> Build OKRs (Objectives and Key Results) for the quarter: 1. 3 Objectives: inspiring, qualitative statements of what you want to achieve 2. For each Objective, 3-4 Key Results: - Specific and measurable (number, percentage, yes/no) - Ambitious but achievable (70% completion = success) - Outcome-based, not activity-based ("increase revenue by 15%" not "send 50 emails") 3. Alignment check: how each OKR connects to the broader team or company goal 4. Scoring rubric: exactly how to measure 0%, 50%, 70%, and 100% for each KR 5. Weekly check-in template: 5 questions to ask every week about OKR progress 6. Mid-quarter assessment: what to evaluate at the halfway point 7. Common OKR mistakes: pitfalls to avoid (too many, not measurable, sandbagging, etc.) OKRs work because they force clarity. If you cannot measure it, you cannot manage it. </task>

Builds quarterly OKRs with measurable key results, scoring rubrics, and weekly check-in templates.

💡

Pro tip: The most common OKR mistake is setting key results that are activities (write 10 blog posts) instead of outcomes (increase organic traffic by 25%). Outcomes let you find the best path. Activities lock you into one approach.

90-Day Sprint Planner

18/35

<context> Primary goal for next 90 days: [DESCRIBE] Why 90 days: [DEADLINE / QUARTERLY / PERSONAL MILESTONE] Current baseline: [WHERE I AM NOW] Target: [WHERE I WANT TO BE IN 90 DAYS] Hours per week available: [FOR THIS GOAL SPECIFICALLY] Obstacles I expect: [LIST] </context> <task> Plan a 90-day sprint: 1. Goal specification: make the target so clear that success/failure is unambiguous 2. Reverse engineering: work backward from the 90-day target to weekly milestones 3. Month 1 (Foundation): what systems, habits, and structures to build 4. Month 2 (Acceleration): where to push harder once the foundation is set 5. Month 3 (Completion): the final push with specific daily targets 6. Weekly cadence: what each week should look like (specific activities) 7. Checkpoint schedule: weekly 10-minute reviews and monthly 30-minute deep reviews 8. Failure modes: the 3 most likely reasons this sprint fails and pre-planned responses 9. Accountability: who knows about this goal and how they help me stay on track 10. Reward: what I earn when I hit the 90-day target (make it real and motivating) 90 days is long enough to achieve something meaningful and short enough to maintain urgency. </task>

Plans a structured 90-day sprint with monthly phases, weekly cadence, failure mode prevention, and accountability.

💡

Pro tip: Tell 3 people about your 90-day goal and schedule monthly check-ins with them. Social accountability is the single most reliable motivation tool when willpower runs out.

Habit Stacking System

19/35

<context> Habits I want to build: [LIST 3-5 NEW HABITS] Existing daily routine: [DESCRIBE YOUR TYPICAL DAY'S ANCHORS — wake up, meals, commute, etc.] Habits I have tried and failed to build: [LIST WITH WHY THEY FAILED] Motivation level: [HIGH / MODERATE / LOW] Environment: [DESCRIBE — home, office, gym access, etc.] </context> <task> Design a habit stacking system: 1. Anchor identification: existing habits that are already automatic (brushing teeth, morning coffee, arriving at desk) 2. Stack design: attach each new habit to an existing anchor using the formula "After I [existing habit], I will [new habit]" 3. Minimum viable habits: shrink each habit to its tiniest version (2 minutes or less) 4. Progression plan: how each habit expands from tiny to full size over 4 weeks 5. Environment design: one change to my physical space for each habit that makes it easier 6. Friction reduction: remove barriers between the anchor and the new habit 7. Tracking method: a simple, visible tracking system (not an app I will forget) 8. Recovery protocol: what to do when I miss a day (not "start over" — restart immediately) 9. 30-day commitment: a specific contract with myself for the first 30 days Make habits so small that skipping them feels ridiculous. You can always do more than the minimum. </task>

Attaches new habits to existing routines using habit stacking with progressive difficulty and environment design.

💡

Pro tip: The secret to habit building is making the habit so small it is impossible to fail. "Do one push-up after brushing teeth" is better than "work out for 30 minutes" because the first one actually happens every day.

Progress Review System

20/35

<context> Goals I am tracking: [LIST WITH CURRENT STATUS] Time period: [WEEKLY / MONTHLY / QUARTERLY REVIEW] Current tracking method: [DESCRIBE — spreadsheet, app, journal, nothing] How I feel about my progress: [DESCRIBE] </context> <task> Create a progress review system: 1. Dashboard design: the 5-7 metrics that capture my progress at a glance 2. Review template: - What went well this period (celebrate first) - What did not go as planned (diagnose, do not judge) - What I learned (extract the lesson) - What to adjust (specific changes for next period) - What to continue (what is working — do not change what works) 3. Leading vs lagging indicators: am I tracking the right things? 4. Trend analysis: how to spot patterns across multiple review periods 5. Course correction protocol: when to adjust the goal vs adjust the approach 6. Motivation maintenance: how to stay motivated when progress is slow 7. Review schedule: specific dates and times blocked for reviews 8. Simplification: how to make the review take 15 minutes maximum Reviewing progress without changing behavior is journaling. Reviewing and adjusting is management. </task>

Creates a lightweight progress review system with dashboard metrics, review templates, and course correction protocols.

💡

Pro tip: Keep the review short and actionable. The purpose is not self-analysis — it is course correction. 15 minutes of honest review and one specific adjustment beats an hour of introspective journaling.

Decision Making

5 prompts

Decision Framework Selector

21/35

<context> Decision to make: [DESCRIBE THE DECISION] Stakes: [LOW / MEDIUM / HIGH — what is at risk] Reversibility: [EASILY REVERSED / HARD TO REVERSE / IRREVERSIBLE] Timeline: [DECIDE BY WHEN] Information available: [HAVE ALL INFO / MISSING KEY INFO / HIGHLY UNCERTAIN] People affected: [WHO AND HOW] </context> <task> Select and apply the right decision framework: 1. Framework recommendation: based on the decision characteristics, which framework fits best: - Pros/cons list (simple decisions) - Weighted scoring matrix (multi-criteria decisions) - Decision tree (sequential decisions with probabilities) - Pre-mortem analysis (high-stakes decisions) - 10/10/10 rule (emotional decisions) - First principles thinking (novel situations) 2. Apply the chosen framework to my specific decision 3. Information gap analysis: what do I still need to know and how to find it 4. Bias check: which cognitive biases are most likely affecting this decision (sunk cost, confirmation, anchoring, etc.) 5. Decision timeline: when to decide and what waiting costs vs what it gains 6. Reversibility plan: if I can reverse this, the exit criteria and timeline 7. Final recommendation: what to do and why The quality of your decisions determines the quality of your life. Use the right tool for each decision. </task>

Matches the right decision framework to your specific situation and applies it with bias checking and reversibility planning.

💡

Pro tip: For most decisions, deciding quickly and adjusting is better than deciding slowly and getting it right. Speed matters more for reversible decisions. Rigor matters more for irreversible ones.

Pre-Mortem Analysis

22/35

<context> Decision or plan: [DESCRIBE WHAT YOU ARE ABOUT TO DO] Stakes: [WHAT IS AT RISK] Timeline: [WHEN RESULTS WILL BE KNOWN] Team involved: [WHO IS EXECUTING] Confidence level: [HOW CONFIDENT ARE YOU THIS WILL WORK] </context> <task> Conduct a pre-mortem analysis: Imagine it is [future date] and this plan has failed spectacularly. Now work backward: 1. Failure scenarios: generate 10 specific ways this could fail 2. For each scenario: - How likely is this? (1-10) - How severe would it be? (1-10) - What early warning signs would we see? - What could we do NOW to prevent it? 3. The "silent killer": the failure mode nobody is talking about (the one everyone is too optimistic to mention) 4. Assumption audit: list every assumption this plan makes and assess the risk if each is wrong 5. Kill criteria: what specific outcomes would cause us to abandon this plan before completion 6. Contingency plans: for the top 3 failure modes, a specific Plan B 7. Updated confidence: after this analysis, how confident am I now? What changed? Pre-mortems prevent disasters that post-mortems only explain. </task>

Runs a pre-mortem analysis to identify failure modes, silent killers, and untested assumptions before executing a plan.

💡

Pro tip: The pre-mortem is most powerful in groups. Asking "how could this fail?" gives people permission to voice concerns they would suppress in a normal planning meeting. Do this for every major decision.

Career Decision Evaluator

23/35

<context> Decision: [DESCRIBE — job change, career pivot, promotion, starting a business, going back to school, etc.] Current situation: [DESCRIBE YOUR CURRENT ROLE AND SATISFACTION] Options: [LIST ALL OPTIONS INCLUDING STAYING PUT] Factors that matter: [MONEY / GROWTH / PURPOSE / LIFESTYLE / LOCATION / PEOPLE / AUTONOMY] Risk tolerance: [CONSERVATIVE / MODERATE / AGGRESSIVE] Dependents: [PEOPLE WHO DEPEND ON YOUR INCOME] </context> <task> Evaluate this career decision: 1. Weighted scorecard: rate each option on every factor that matters (1-10), weighted by importance 2. Financial analysis: compare compensation, benefits, growth trajectory, and financial risk across options 3. Regret minimization: at age 80, which decision would I regret NOT making? 4. Optionality analysis: which choice opens the most future doors vs closes them? 5. Identity alignment: which option aligns with who I want to become, not just what I want to have? 6. Worst case scenario: for each option, what is the absolute worst that could happen? 7. Reversibility assessment: which options can I reverse if they do not work out? 8. 1-year and 5-year projection: where each option likely leads 9. The voice of fear vs the voice of wisdom: distinguish between legitimate concerns and unfounded anxiety 10. Recommendation: with reasoning Career decisions are not just about the next step. They are about the trajectory each step puts you on. </task>

Evaluates a career decision through weighted scoring, regret minimization, optionality analysis, and trajectory projection.

💡

Pro tip: Ask yourself: "Which option would make for a better story in 10 years?" This question bypasses short-term fear and taps into your deeper sense of what a meaningful life looks like.

Information-to-Action Converter

24/35

<context> Research or data I have gathered: [PASTE OR DESCRIBE] Decision this informs: [WHAT I NEED TO DECIDE] Analysis paralysis level: [LOW / MEDIUM / HIGH] Deadline: [WHEN I MUST DECIDE] </context> <task> Convert my research into a clear decision: 1. Key findings: distill all research into 5-7 critical insights 2. So-what analysis: for each finding, what does it mean for my decision? 3. Contradictions: where does the data conflict? How to resolve it? 4. Missing information: what do I still not know? Can I decide without it? 5. The 80% rule: do I have enough information to make a good (not perfect) decision? 6. Options narrowing: based on the data, eliminate options that are clearly inferior 7. Decision statement: "Based on [evidence], I will [action] because [reasoning]" 8. Action plan: the first 3 things to do after deciding Information without action is entertainment. The purpose of research is to enable a decision, not to postpone it. </task>

Transforms research and gathered information into a clear decision with action steps and an 80% sufficiency assessment.

💡

Pro tip: If you have been researching for more than twice the time you estimated, you are procrastinating through research. Set a research deadline. When it arrives, decide with what you have.

Trade-Off Analyzer

25/35

<context> Situation: [DESCRIBE THE TRADE-OFF] Option A: [DESCRIBE WITH BENEFITS AND COSTS] Option B: [DESCRIBE WITH BENEFITS AND COSTS] What makes this hard: [WHY YOU CANNOT JUST CHOOSE] Values in conflict: [WHAT VALUES ARE PULLING IN DIFFERENT DIRECTIONS] </context> <task> Analyze this trade-off: 1. Make the trade-off explicit: what specifically am I giving up with each option? 2. Asymmetric consequences: are the downsides of each option equally bad, or is one much worse? 3. Time dimension: how does this trade-off look at 1 month, 1 year, and 5 years? 4. Values clarification: which of my conflicting values is more central to who I am? 5. The "hell yes or no" test: does either option spark genuine excitement? 6. Third option search: is there a creative option that reduces the trade-off? 7. Reversibility: can I try one option first and switch to the other if it does not work? 8. Advice to a friend: if my best friend had this exact dilemma, what would I tell them? 9. The coin flip test: flip a (mental) coin — does the result make me relieved or disappointed? 10. Decision: with reasoning Most difficult decisions are difficult because both options are good. That is a good problem to have. </task>

Analyzes a difficult trade-off through multiple lenses including time horizon, values, reversibility, and the coin flip test.

💡

Pro tip: The coin flip test works: assign each option to a side of a coin and flip it. Your immediate emotional reaction to the result tells you what you actually want. The coin does not decide — your reaction does.

Frequently Asked Questions

Claude is a powerful thinking partner for productivity, but it cannot do the work for you. The prompts in this guide help you plan better, prioritize smarter, and design systems that reduce friction. The actual productivity gain comes from implementing the systems Claude helps you design. Think of Claude as a productivity consultant who is available 24/7 — the value depends on whether you follow the advice.
Claude excels at structured, analytical productivity work: decision frameworks that require weighing multiple factors, project decomposition that needs to track dependencies, and review systems that maintain consistency across long documents. For quick brainstorming or simple task lists, both tools work well. For deep system design, Claude's analytical nature produces more thorough, internally consistent frameworks.
Use Claude for system design and weekly/monthly planning, not daily task management. Your daily planning should take 10 minutes using a system Claude helped you build — not 30 minutes in a Claude conversation. Design the system once with Claude, then execute it with a simple tool (paper, calendar, task app). Revisit Claude when the system needs adjustment.
Many prompts in this guide work for teams with minor modifications. Meeting optimization, OKR building, delegation frameworks, and decision-making processes all apply to teams. Share the outputs with your team as proposed systems. Claude can also help you design team processes, meeting agendas, and collaboration frameworks specifically for your team dynamics.
Failed systems usually fail for one of three reasons: too complex to maintain, not aligned with how you actually work, or no accountability mechanism. The prompts in this guide help you design systems that match YOUR work patterns and constraints. Start with one system (daily planning or weekly review), master it, then add another. Building one habit at a time succeeds where overhauling everything at once fails.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

14-day free trial. Cancel anytime.