Get More Done in Less Time — With AI as Your Productivity Partner
35 copy-paste prompts for planning, prioritization, meeting management, email efficiency, and habit building — ready to transform your workflow.
Planning & Prioritization
6 promptsWeekly Planning Session
1/35Help me plan my upcoming week. Here are my open tasks and commitments: [List your tasks, meetings, and deadlines] My top goal this week is: [state your #1 objective] My available work hours each day are: [e.g., 9am–6pm with 1hr lunch] My energy tends to be highest in the: [morning / afternoon / evening] Create a day-by-day plan that: 1. Schedules my most important work during my peak energy hours 2. Batches similar tasks to minimize context switching 3. Leaves 20% buffer time for unexpected tasks 4. Flags any tasks that should be delegated or dropped 5. Ends each day with a clear shutdown ritual Format the output as a clean daily schedule with time blocks.
Turns a messy list of tasks and commitments into a structured, realistic weekly plan aligned to your energy and priorities.
Pro tip: Run this every Sunday evening. The 10 minutes it takes saves hours of reactive decision-making throughout the week.
Eisenhower Matrix Sorter
2/35I have the following list of tasks on my plate: [Paste your task list] Sort every item into the Eisenhower Matrix using these definitions: - Quadrant 1 (Do Now): Urgent and important — deadlines, crises, critical deliverables - Quadrant 2 (Schedule): Not urgent but important — strategic work, relationship-building, learning - Quadrant 3 (Delegate): Urgent but not important — interruptions, some meetings, admin requests - Quadrant 4 (Eliminate): Not urgent and not important — busywork, time-wasting activities For each quadrant, list the tasks and give me one sentence on the right action to take. Flag any tasks you are uncertain about and explain why. At the end, tell me the 3 tasks I should start today.
Instantly categorizes your entire task list into the four Eisenhower quadrants so you act on the right things first.
Pro tip: Most people have too many Quadrant 1 items because they neglect Quadrant 2. If your Q1 list is long, that is a signal to invest more in planning and prevention.
Time Blocking Schedule
3/35Build a time-blocked schedule for tomorrow based on the following: Tasks to complete: [list tasks with estimated durations] Fixed commitments: [list meetings or appointments with times] Deep work capacity: [how many hours can you focus without interruption] Administrative tasks: [email, Slack, reviews — how long do these typically take] Personal constraints: [school pickup, gym, hard stop time, etc.] Create a schedule that: 1. Protects at least one uninterrupted deep work block of 90+ minutes 2. Batches all communication (email/Slack) into 2 defined windows 3. Places shallow tasks in low-energy time slots 4. Includes a 10-minute review at end of day 5. Marks any tasks that will not fit and need to be rescheduled Output as a clean hour-by-hour schedule.
Builds a practical time-blocked day that protects deep work while fitting in meetings, admin, and personal constraints.
Pro tip: Add 25% buffer to every task estimate. If you think something takes 30 minutes, block 40. Schedules without buffers collapse by 11am.
Quarterly Goal Setter
4/35Help me set meaningful goals for the next 90 days. Here is my context: My role: [job title and main responsibilities] My top priority this quarter from my manager or company: [state it] Personal goals I want to make progress on: [list 2-3] Current biggest bottleneck in my work: [describe it] Capacity constraints this quarter: [vacations, big projects, deadlines] Using the OKR framework (Objectives and Key Results), create: 1. One professional Objective with 3 measurable Key Results 2. One personal Objective with 2-3 measurable Key Results 3. One skill or learning goal with a clear 90-day milestone For each goal, add: Why it matters, How I will track it weekly, and One early warning sign I am off track.
Structures your quarterly goals using the OKR framework with built-in tracking signals and early warning indicators.
Pro tip: Quarterly goals work best when reviewed weekly, not monthly. Schedule a 15-minute Friday review to check your Key Results and adjust tactics.
Project Breakdown
5/35I need to break down this project into an actionable plan: Project name: [name] End goal / deliverable: [describe what done looks like] Deadline: [date] Team involved: [just me / list team members and their roles] Known dependencies or blockers: [anything that must happen before you can start or finish] Risk factors: [what could go wrong] Create a complete project breakdown that includes: 1. Project phases with start and end dates 2. All tasks within each phase, with estimated time and owner 3. Key milestones and review checkpoints 4. Top 3 risks with mitigation strategies 5. Definition of done — exact criteria for project completion 6. Recommended first 3 actions to take this week Format as a structured plan I can paste into a project management tool.
Transforms a vague project goal into a phased, time-estimated, risk-aware action plan ready for execution.
Pro tip: The first 3 actions are the most important output. Momentum matters more than perfect planning — start moving within 24 hours of setting the plan.
Decision Matrix
6/35I need to make a decision between the following options: Decision I am facing: [describe the decision] Options I am considering: 1. [Option A] 2. [Option B] 3. [Option C, if applicable] Criteria that matter most to me (ranked by importance): 1. [Criterion 1, e.g., time to implement] 2. [Criterion 2, e.g., cost] 3. [Criterion 3, e.g., long-term impact] 4. [Criterion 4, if applicable] Context: [Any constraints, preferences, or background the model should know] Build a weighted decision matrix scoring each option against each criterion from 1–10. Show the math, declare the winning option, and list the top 2 reasons to choose it and the top 1 risk to watch for.
Turns a difficult multi-option decision into a scored, weighted analysis so you can choose with confidence instead of gut feel.
Pro tip: If the matrix points to Option A but your gut wants Option B, that gut reaction is data. Explore why before committing — sometimes the criteria weights are wrong.
Prompts get you started. Tutorials level you up.
A growing library of 300+ hands-on AI tutorials. New tutorials added every week.
Meeting Management
6 promptsMeeting Agenda Builder
7/35Create a focused meeting agenda for the following: Meeting purpose: [what decision needs to be made or what outcome is needed] Attendees and their roles: [list names/roles] Duration: [30 / 45 / 60 minutes] Context: [any background the attendees need to come prepared] Pre-work required: [anything attendees should read or prepare in advance] Build an agenda that: 1. Opens with the desired outcome stated clearly (not just a topic) 2. Allocates time to each agenda item 3. Assigns a discussion lead for each item 4. Includes a 5-minute decision and action items capture at the end 5. Ends on time with no item left open-ended Also write a 3-sentence pre-meeting message I can send to attendees that explains the goal and what to prepare.
Creates a structured, time-allocated meeting agenda with a pre-meeting briefing message so attendees show up prepared.
Pro tip: Always state the desired outcome at the top of the agenda, not just the topic. "Discuss Q3 budget" is a topic. "Approve Q3 budget allocation" is an outcome — and it runs a much tighter meeting.
Meeting Notes Summarizer
8/35Here are the raw notes or transcript from a meeting I just had: [Paste your meeting notes or transcript] Create a clean, shareable meeting summary that includes: 1. Meeting date and attendees 2. One-paragraph executive summary (3–5 sentences, what was decided and why) 3. Key discussion points, organized by topic (not chronologically) 4. Decisions made — list each decision clearly 5. Action items table: Task | Owner | Due Date 6. Open questions or items deferred to next meeting 7. Next meeting date and agenda preview (if discussed) Keep the tone professional and concise. Avoid re-stating the entire discussion — capture only what matters for people who were not in the room.
Transforms messy meeting notes or transcripts into a crisp, shareable summary with clear decisions and action items.
Pro tip: Send the meeting summary within 2 hours while context is fresh. The faster it goes out, the higher the follow-through rate on action items.
Action Items Extractor
9/35Read the following meeting transcript or notes carefully: [Paste your meeting notes or transcript] Extract every action item mentioned explicitly or implied. For each action item: 1. Describe the task clearly in one sentence using active voice 2. Identify the owner (person responsible) 3. Capture the due date or urgency level (if stated) 4. Note any dependencies (what must happen before this can be done) 5. Flag any action items where the owner is unclear Organize the output as a table with columns: Task | Owner | Due Date | Dependencies | Status (default: Open). Also list any commitments that were made verbally but not assigned to a clear owner — these need follow-up before the meeting ends.
Extracts every action item from meeting notes, assigns ownership, and flags unassigned commitments that fall through the cracks.
Pro tip: Copy this table directly into your project management tool. Unassigned action items are the #1 reason meetings do not produce results.
Meeting Necessity Evaluator
10/35I have been invited to (or am considering scheduling) the following meeting: Meeting title: [title] Stated purpose: [what it says on the invite] Attendees: [who is invited] Duration: [length] My role in the meeting: [presenter / decision-maker / FYI / participant] What I know about the background: [any context] Evaluate whether this meeting is necessary using these criteria: 1. Could this be resolved with a well-written async message or document instead? 2. Is a decision actually required, or is this a status update? 3. Am I the right person to attend, or should I send a delegate? 4. Is 100% of the attendee list necessary, or can some be removed? Give me a clear recommendation: Attend / Decline / Propose Async / Shorten. Then write a polite message for whichever action is recommended.
Evaluates whether a meeting is truly necessary and drafts the appropriate response — attend, decline, or propose an async alternative.
Pro tip: Protecting your calendar is a skill. Use this prompt before accepting any meeting over 30 minutes that does not have a clear decision on the agenda.
Async Update Writer
11/35I need to write an async update to replace a meeting or weekly check-in. Here is the context: Audience: [who will read this — team, manager, stakeholders] Purpose: [status update / decision request / blocker escalation / project recap] Key information to communicate: - Progress this week: [what got done] - In progress: [what is being worked on now] - Blockers: [anything slowing progress or needing help] - Decisions needed: [any approvals or input required] - Next steps: [what happens next and by when] Write a well-structured async update that: 1. Leads with the most important thing the reader needs to know 2. Uses headers or bullets so it can be scanned in under 60 seconds 3. Makes any decision requests or questions crystal clear 4. Ends with a call to action or response deadline if needed Tone: [professional / casual / direct]
Writes a structured, scannable async update that communicates progress, blockers, and decisions without scheduling a meeting.
Pro tip: The best async updates are written for someone who has 60 seconds to read them. Lead with the headline, not the backstory.
Standup Prep
12/35Help me write a focused daily standup update. Here is my context for today: Yesterday I completed: [list tasks finished] Today I plan to work on: [list today's priorities] Blockers or help needed: [anything slowing me down or that I need from a teammate] Any context the team should know: [optional — meetings, out-of-office, context switches] Write a standup update that: 1. Is under 90 seconds to read aloud 2. States yesterday's progress with one concrete result (not just "worked on X") 3. States today's plan as outcomes, not activities 4. Makes any blocker specific and actionable (who can help and how) 5. Avoids filler phrases like "no blockers, just busy" Also flag if my today plan seems overloaded and suggest what to defer.
Drafts a crisp, outcome-focused standup update that communicates real progress and surfaces real blockers in under 90 seconds.
Pro tip: Say "I shipped the onboarding email flow" not "I worked on the email." Outcome language signals accountability and helps your manager spot when you are overloaded.
Email & Communication
6 promptsEmail Reply Drafter
13/35Draft a reply to this email: [Paste the email you received] Context about my situation: - My relationship to the sender: [colleague / client / manager / vendor / stranger] - What I want to accomplish with this reply: [inform / agree / push back / ask a question / decline] - Tone I want: [professional and warm / direct and brief / formal / casual] - Key points I must include: [list any non-negotiable content] - What I do NOT want to say or commit to: [any constraints] Write a reply that: 1. Opens with a direct, confident first sentence (no "Hope you are doing well") 2. Addresses every question or request in the original email 3. States my position or answer clearly with no ambiguity 4. Closes with a clear next step or call to action 5. Stays under [150 / 200 / 300] words
Drafts a focused, clear email reply that addresses every point in the original message without filler phrases or ambiguity.
Pro tip: Delete the opening pleasantry. Emails that start with the main point get read and replied to faster than those that start with "Hope this finds you well."
Email Summarizer
14/35I have the following email thread I need to get up to speed on quickly: [Paste the full email thread] Summarize this thread by providing: 1. One-sentence headline: what is this thread actually about 2. Key context: the background a new reader needs (3–5 sentences) 3. Current status: where things stand right now 4. Decisions made: list any commitments or agreements reached 5. Outstanding questions or unresolved issues 6. What is expected of me (if anything): any action I need to take 7. The most important email in the thread and why Keep the summary under 200 words. Use bullets where possible.
Distills a long email thread into a fast, structured briefing so you can act without re-reading every message.
Pro tip: Use this before rejoining a thread you have been on vacation from or before a meeting where an email thread will be discussed.
Slack Message Optimizer
15/35Rewrite the following Slack message (or draft a new one) to be clearer and more actionable: Original message or context: [paste your draft or describe what you need to communicate] Channel or recipient: [public channel / DM / group DM] Goal: [inform the team / get a decision / ask for help / share an update / escalate an issue] Urgency: [immediate / by end of day / no rush] Rewrite this as a Slack message that: 1. Leads with the core point in the first line (Slack shows only a preview) 2. Uses formatting (bold, bullets, code blocks) only where it genuinely improves clarity 3. Makes any ask or decision needed absolutely explicit 4. States a response deadline if one exists 5. Stays under 150 words unless more detail is essential Also suggest whether this should be a thread reply, a new message, or a DM instead.
Rewrites Slack messages to lead with the point, make asks explicit, and respect everyone's attention span.
Pro tip: The first line of your Slack message is the most important — it is what people see in their notification. Lead with the headline, not the setup.
Difficult Conversation Prep
16/35I need to have a difficult conversation and want to prepare what to say. Here is the situation: Who I am talking to: [their role and relationship to me] What the issue is: [describe the problem clearly and factually] What outcome I want from this conversation: [what needs to change or be agreed upon] What I am worried they will say: [anticipated objections or emotional reactions] What I am afraid of: [being honest here helps get better prep] Help me prepare by: 1. Writing an opening statement that is direct but not accusatory (under 60 seconds to say) 2. Listing 3 likely responses they might have and how I should answer each 3. Identifying the one non-negotiable for me in this conversation 4. Suggesting what I should do if the conversation gets emotional or defensive 5. Writing a closing statement that moves toward a next step Tone: honest, calm, and solution-focused.
Prepares you for a difficult workplace conversation with an opening statement, anticipated responses, and a solution-focused closing.
Pro tip: Practice your opening statement out loud before the conversation. The first 30 seconds set the tone for everything that follows.
Status Update Writer
17/35Write a project or work status update for the following audience and context: Project or initiative name: [name] Audience: [manager / leadership / client / full team] Update frequency: [weekly / bi-weekly / monthly / ad hoc] Status overall: [On Track / At Risk / Off Track] Period covered: [date range] Key updates this period: - Completed: [list what was finished] - In progress: [what is actively being worked on] - Risks or issues: [anything that could impact timeline or quality] - Decisions needed from audience: [any approvals, inputs, or escalations] - Next milestones: [what is coming up and when] Write a concise status update that: 1. States overall health clearly and immediately 2. Highlights wins and progress before problems 3. Frames risks as "here is what we are doing about it" 4. Ends with a clear ask or next step if one is needed 5. Can be read in under 2 minutes
Writes a clear, credibility-building status update that leads with health, highlights progress, and frames risks constructively.
Pro tip: Never bury bad news at the bottom of a status update. Flag risks early with your mitigation plan already attached — that is what builds trust with leadership.
Delegate Task Message
18/35I need to delegate a task to a colleague or direct report and want to communicate it clearly. Here is the task: Task description: [what needs to be done] Person I am delegating to: [their role and experience level with this type of task] Deadline: [when it is due] Expected output / deliverable: [exactly what done looks like] Resources available to them: [tools, docs, people they can ask] Decision-making authority: [what they can decide on their own vs. what needs my approval] How I want to be updated: [check-ins, final review only, etc.] Write a delegation message that: 1. Explains the what and why (context matters for quality) 2. States the deliverable and deadline with no ambiguity 3. Clarifies their authority level so they do not over-ask or under-ask 4. Offers support without micromanaging 5. Ends with a confirmation ask so I know they understand
Writes a clear delegation message that gives context, defines the deliverable, and sets the right authority level to avoid bottlenecks.
Pro tip: The most common delegation failure is not the "what" — it is the "so they can decide this on their own vs. check with me first." Be explicit about authority boundaries.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.
Focus & Deep Work
6 promptsDistraction Audit
19/35I want to identify and address the main distractions that are hurting my focus. Help me run a distraction audit. My work environment: [home / open office / private office / hybrid] Biggest distractions I am aware of: [list them honestly] How my day currently looks: [describe a typical day — when focus happens, when it does not] Tools I use for communication: [Slack, email, phone, etc. and how often I check them] My typical response to distractions: [do I give in immediately, resist for a while, etc.] Analyze my situation and provide: 1. The top 3 distraction patterns and why each is costing me time 2. A specific fix for each one (not generic advice — make it actionable for my context) 3. A recommended communication policy (when I check messages and when I do not) 4. Environment changes to make focus easier 5. A 30-day experiment to test these fixes with a simple tracking method
Identifies your specific distraction patterns and creates a customized plan to protect focus time with measurable changes.
Pro tip: Track your actual focus time for 3 days before running this prompt. Gut estimates of distraction are almost always wrong — the data is more honest.
Deep Work Schedule
20/35Help me design a sustainable deep work schedule. Here is my current situation: Job type and main responsibilities: [describe your role] Current weekly hours I spend on truly focused work: [honest estimate] Goal: [how many hours of deep work per week I want to achieve] Meetings I cannot move: [list recurring meetings and their times] Personal constraints: [commute, family, energy patterns, etc.] Biggest obstacle to deep work right now: [be honest] Design a deep work schedule that: 1. Carves out at least [X] hours of protected deep work per day/week 2. Works around my fixed meetings and constraints 3. Uses a specific deep work philosophy (Newport's monastic / bimodal / rhythmic — recommend the best fit for me) 4. Includes rules for what counts as deep work vs. shallow work 5. Has a shutdown ritual to signal the end of the workday 6. Can realistically start this Monday
Designs a personalized deep work schedule using Cal Newport's framework, adapted to your actual constraints and meeting reality.
Pro tip: Rhythmic scheduling (same time every day) works for most knowledge workers because it removes the daily decision about when to do deep work. The best time is the time you actually protect.
Pomodoro Session Planner
21/35I have [X hours] available for focused work today. Help me plan a Pomodoro session schedule for the following tasks: Tasks to complete: 1. [Task name] — estimated effort: [low / medium / high] 2. [Task name] — estimated effort: [low / medium / high] 3. [Task name] — estimated effort: [low / medium / high] My preferred Pomodoro structure: [25/5 classic / 50/10 extended / custom] Energy level right now: [high / medium / low] Any fixed breaks or commitments during this window: [list them] Build a Pomodoro schedule that: 1. Sequences tasks from highest to lowest cognitive demand if energy is high, reverse if energy is low 2. Groups small tasks into single Pomodoros to avoid transition waste 3. Places a longer break (15–30 min) after every 4 Pomodoros 4. Accounts for my fixed commitments 5. Flags if my task list is too ambitious for the available time
Builds a Pomodoro-based work session schedule that sequences tasks by cognitive demand and respects your energy level.
Pro tip: If the prompt flags your list as too ambitious, do not ignore it. Choose the top 2 tasks and commit. Finishing 2 things beats starting 5.
Context Switching Reducer
22/35I am constantly context-switching between tasks and it is killing my productivity. Help me reduce it. My current situation: [describe how your day typically goes — how often you switch tasks and why] Types of work I do: [list the main categories — e.g., writing, coding, meetings, email, strategy] Main triggers of unplanned switching: [Slack pings, manager requests, own impulse, etc.] What I have already tried: [any systems or strategies attempted] Team expectations around responsiveness: [do you need to respond within minutes, hours, or can you batch?] Create a plan to reduce context switching that: 1. Groups my work types into batches (and suggests the right sequence) 2. Designs a response policy that is acceptable to my team but protects focus 3. Identifies the one context switch I can eliminate immediately 4. Suggests how to communicate my focus policy to my team or manager 5. Gives me a 1-week test to validate whether it is working
Diagnoses your context-switching triggers and builds a batching and response policy that protects focus without isolating you from your team.
Pro tip: Every unplanned task switch costs 23 minutes of recovery time on average. Even reducing switches by 3 per day recovers over an hour of focused output.
Energy Management Plan
23/35Help me build a personal energy management plan so I am doing the right work at the right time. My typical daily energy pattern: [describe when you feel sharpest, when you crash, when you get a second wind] My work schedule: [start time, end time, any fixed constraints] Types of work and their cognitive demand: - High cognitive demand tasks: [examples — writing, complex analysis, coding] - Medium demand tasks: [examples — emails, reviews, planning] - Low demand tasks: [examples — admin, data entry, filing] Lifestyle factors affecting energy: [sleep quality, exercise habits, nutrition, stress level] Create an energy management plan that: 1. Maps my energy curve to specific time blocks 2. Assigns task types to the right energy windows 3. Identifies 2-3 energy leaks I should fix (based on my inputs) 4. Designs a pre-work ritual to prime my best morning focus 5. Includes a mid-day reset to recover afternoon energy 6. Suggests one habit change that would have the highest energy ROI
Maps your energy curve to your task types and builds a daily rhythm that maximizes output without burning out.
Pro tip: Most people discover they have only 3-4 hours of genuine peak cognitive capacity per day. Guard those hours like revenue — they are your most valuable asset.
Procrastination Breaker
24/35I am procrastinating on this task and need help getting started: Task I am avoiding: [describe it] How long I have been putting it off: [hours / days / weeks] Why I think I am avoiding it (be honest): - Is it unclear what "done" looks like? [yes/no] - Does it feel too big to start? [yes/no] - Am I afraid of doing it wrong or being judged? [yes/no] - Is it boring or low intrinsic motivation? [yes/no] - Something else: [describe] Deadline: [when does this actually need to be done] Based on my answers, diagnose the root cause of my procrastination and give me: 1. The specific reason I am avoiding this (not generic) 2. The single smallest possible action I can take in the next 5 minutes 3. How to make the task feel less threatening or overwhelming 4. A commitment device I can use to follow through 5. What I will feel once it is done (make it real)
Diagnoses the root cause of your specific procrastination and gives you a 5-minute entry point to break the avoidance pattern.
Pro tip: The 5-minute action is the key. You are not committing to finishing — only to starting. Almost always, starting is enough to kill the procrastination loop.
Habits & Systems
6 promptsMorning Routine Designer
25/35Design a morning routine that sets me up for a highly productive day. Here is my situation: Wake-up time (current): [time] Ideal wake-up time: [time] Time available before work or first commitment: [X hours/minutes] Current morning routine (if any): [describe what you do now] Goals for my morning routine: 1. [e.g., improve focus for the workday] 2. [e.g., exercise consistently] 3. [e.g., reduce morning stress] Biggest challenge with mornings right now: [be honest] Hard constraints: [partner schedule, kids, commute, etc.] Design a morning routine that: 1. Fits within my available time window 2. Includes a physical, mental, and intentional element 3. Starts with the lowest-friction action possible (to beat resistance) 4. Has a trigger that signals the start and end of the routine 5. Can be done even on bad or low-energy days (a minimum viable version) 6. Builds to a full version over 30 days Provide both a full version and a 10-minute minimum version.
Designs a personalized morning routine with a full version and a minimum viable version for low-energy days.
Pro tip: The minimum version is what makes the habit stick. You will not always have an hour — but if you always have 10 minutes, you will never break the chain.
Habit Tracker Setup
26/35Help me design a habit tracking system for the following habits I want to build: Habits I want to track: 1. [Habit 1] — frequency goal: [daily / X times per week] 2. [Habit 2] — frequency goal: [daily / X times per week] 3. [Habit 3] — frequency goal: [daily / X times per week] 4. [Additional habits if any] Current tracking method: [paper / app / spreadsheet / nothing] How long I typically stick with habit tracking before giving up: [be honest] Biggest challenge with habit consistency: [what usually derails me] Preferred review frequency: [daily / weekly] Design a habit tracking system that: 1. Is simple enough to maintain during a bad week 2. Includes a specific daily trigger for logging (when and how) 3. Has a weekly review prompt to identify patterns 4. Celebrates streaks without triggering shame when streaks break 5. Includes a monthly format review — is this system still working? Also recommend whether paper, an app, or a spreadsheet best fits my situation.
Designs a friction-free habit tracking system with daily triggers, weekly reviews, and failure-resilient streak logic.
Pro tip: When you miss a day, the only rule is: never miss twice. A single miss is an accident. Two in a row is the start of a new (bad) habit.
Personal Retrospective
27/35Run a personal retrospective on the past [week / month / quarter] with me. Here is my raw data: What I accomplished: [list key outputs and wins] What I failed to complete or finish: [be honest] Moments I felt most energized and productive: [describe] Moments I felt drained, distracted, or low-output: [describe] Habits I kept: [list] Habits I broke or neglected: [list] Biggest unexpected challenge: [describe] Biggest unexpected win: [describe] Using this data, provide a retrospective that covers: 1. What went well — top 3 wins and why they happened 2. What did not go well — top 3 failures with root cause, not surface explanation 3. What to start doing next period 4. What to stop doing next period 5. What to keep doing next period 6. One specific experiment to run next period 7. One personal insight about myself from this period
Runs a structured personal retrospective using your raw data to surface patterns, root causes, and one focused experiment for the next period.
Pro tip: The root cause question is the most valuable part. "I did not exercise" is not a root cause. "I did not exercise because I scheduled it at 6pm and had no energy left" — that is a root cause you can fix.
System Audit
28/35Audit my current productivity system and identify where it is breaking down. Here is how my system currently works: Task management: [what tool or method I use, how often I review it] Calendar and scheduling: [how I manage my time and meetings] Email and communication: [how I process inbox, how often I check messages] Note-taking and knowledge capture: [where I capture ideas, meeting notes, tasks] Project tracking: [how I track ongoing projects and deadlines] Weekly review: [do I have one, how does it work, how consistently] For each area, identify: 1. The specific way this part of my system is failing or creating friction 2. The downstream effect of that failure on my productivity 3. One change that would have the highest impact At the end, give me a prioritized list of the top 3 system fixes to implement this month, starting with the one that will give me the fastest relief.
Audits every component of your productivity system to find where friction and failures are accumulating and prioritizes the highest-ROI fixes.
Pro tip: A productivity system that requires willpower to maintain will fail every time. The audit often reveals that the fix is simplification, not adding more tools or steps.
Second Brain Organizer
29/35Help me design a second brain knowledge management system that I will actually use. Here is my context: What I want to capture: [meeting notes / ideas / research / articles / book highlights / project thinking] Tools I currently use or am open to: [Notion / Obsidian / Roam / Apple Notes / other] How I best retrieve information: [searching by keyword / browsing folders / seeing connections / following links] How many notes I currently have (rough): [number or "starting from scratch"] Biggest frustration with my current note system: [what makes you not use it] Design a second brain system that: 1. Uses the simplest possible folder or tagging structure for my use case 2. Defines a clear capture workflow (where notes go when I first take them) 3. Has a weekly processing ritual to file and connect new notes 4. Makes retrieval fast (defines how I find what I saved) 5. Grows with me without becoming a burden to maintain Include a starter template for the top 3 note types I will use most.
Designs a personalized second brain system with a capture workflow, filing structure, and starter templates matched to how you actually think.
Pro tip: The capture step is where every second brain system fails. If capturing a note takes more than 10 seconds, you will stop doing it. Optimize for speed of capture first, organization second.
Reading Notes Processor
30/35I just finished reading [book title / article title / report] and want to extract maximum value from it. Here are my raw highlights and notes: [Paste your highlights, notes, or key quotes] Process these into a permanent, useful knowledge note by: 1. Writing a 3-sentence summary of the core thesis or main idea 2. Extracting the top 5 most actionable insights (not just interesting — actionable) 3. Identifying 2-3 ideas that connect to things I already know or believe 4. Writing 3 questions this reading raised that I want to explore further 5. Creating one "so what" statement: how does this change what I think or do? 6. Suggesting 2-3 related books, articles, or thinkers to explore next 7. Writing a tweet-length summary I could share with someone in 60 seconds Format the output as a clean knowledge note I can save to my second brain.
Transforms raw reading highlights into a permanent, actionable knowledge note with insights, connections, and follow-up questions.
Pro tip: The "so what" statement is the most important line. Reading without changing your thinking or behavior is just entertainment. Make this explicit every time.
Go from copy-pasting to actually mastering AI.
AI Academy: 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ other tools. New tutorials added every week.
Automation & Templates
5 promptsRecurring Task Automator
31/35I have a recurring task I do regularly that might be automatable or at least streamlined. Help me analyze it. Task description: [describe the task in detail] How often it recurs: [daily / weekly / monthly] Estimated time per occurrence: [X minutes/hours] Tools I currently use for this task: [list tools] Tools I have access to but do not fully use: [Zapier / Make / Notion automations / Excel macros / other] My technical comfort level: [not technical / comfortable with no-code / can handle some code] Biggest frustration with this task: [what is most tedious or error-prone] Provide: 1. An honest assessment of how automatable this task is (fully / partially / not) 2. The specific automation approach that best fits my tools and skill level 3. Step-by-step instructions to set up the automation 4. What to do with the time saved 5. Any risks or things that could go wrong with the automation
Analyzes a recurring task for automation potential and provides a step-by-step implementation plan matched to your technical skill level.
Pro tip: Focus on tasks you do more than 10 times a month. Even saving 5 minutes per occurrence adds up to an hour of recovered time every month.
SOP Writer
32/35Write a Standard Operating Procedure (SOP) for the following task or process: Process name: [name] Purpose: [why this process exists and what problem it solves] Who performs this process: [role or name] Frequency: [how often it happens] Tools required: [list all tools, software, or access needed] Step-by-step of how I currently do this: [describe what you do, even if informal or inconsistent] Common mistakes or failure points: [where does this go wrong?] How success is measured: [what does a successful completion look like?] Write a clear SOP that includes: 1. Overview and purpose (2-3 sentences) 2. Prerequisites (access, tools, information needed before starting) 3. Step-by-step instructions, numbered, with substeps where needed 4. Decision points clearly flagged (if X then Y, else Z) 5. Quality checks at key steps 6. Common errors and how to fix them 7. Version number and last updated date placeholder
Transforms your informal process knowledge into a structured, repeatable SOP that anyone on your team can follow.
Pro tip: Write SOPs as if the person reading them has never done the task before. The goal is that anyone could execute it correctly on day one without asking a single question.
Checklist Builder
33/35Create a comprehensive checklist for the following process or event: Process or event: [name and describe it] Who uses this checklist: [just me / a team / clients / reports] When it is used: [before, during, or after the process] Consequences of missing a step: [low stakes / medium / high stakes — helps calibrate detail level] Known steps I always do: [list what you currently remember to do] Steps I sometimes forget: [this is the most important input] Tools involved: [relevant software, systems, or physical resources] Build a checklist that: 1. Uses clear, action-oriented language for each item (verb-first) 2. Is organized into logical sections (not one long list) 3. Includes verification steps for high-stakes items 4. Has an estimated time next to each section 5. Ends with a "done" confirmation line Also flag any items where the order matters and explain why.
Creates a well-structured, verb-first checklist with logical sections, time estimates, and verification steps for high-stakes items.
Pro tip: The most valuable checklist items are the ones you sometimes forget — not the ones you always remember. Use the "sometimes forget" input to catch expensive mistakes.
Workflow Optimizer
34/35Help me optimize an existing workflow that feels slow or inefficient. Here is the current workflow: Workflow name: [name] Goal of the workflow: [what it is supposed to produce] Current steps in order: 1. [Step 1 — who does it, how long it takes] 2. [Step 2 — who does it, how long it takes] 3. [Continue for all steps] Handoffs between people or tools: [describe where things get passed and to whom] Bottlenecks I have noticed: [where does it slow down or get stuck] Error-prone steps: [where do mistakes happen most often] Desired improvement: [faster / fewer errors / less manual work / more consistent output] Analyze this workflow and recommend: 1. Steps that can be eliminated entirely 2. Steps that can be combined or parallelized 3. Handoffs that can be reduced or automated 4. The single biggest bottleneck and how to fix it 5. A redrawn workflow map with the improvements applied 6. Estimated time savings per cycle
Analyzes your existing workflow, identifies bottlenecks and waste, and redesigns it with measurable time savings.
Pro tip: Eliminating steps is always more powerful than speeding them up. Before optimizing how something is done, ask whether it needs to be done at all.
Personal Dashboard Designer
35/35Help me design a personal productivity dashboard to track what matters most. Here is my context: My role: [job title and main responsibilities] Top 3 goals this quarter: [list them] Metrics I currently track (if any): [what you measure now] Metrics I feel I should track but do not: [what you wish you measured] Tool I want to use for the dashboard: [Notion / spreadsheet / paper / other] How often I will review it: [daily / weekly / both] Time I can spend maintaining it per week: [X minutes] Design a personal dashboard that: 1. Shows goal progress at a glance (traffic light or percentage) 2. Tracks 3-5 leading indicators that predict whether I will hit my goals 3. Has a weekly input section that takes under 5 minutes to fill in 4. Includes a focus widget — my top 3 priorities for the current week 5. Has a reflection section for weekly retrospective notes Provide the full dashboard structure with column headers, formulas (if spreadsheet), and example data.
Designs a lean personal dashboard with goal tracking, leading indicators, and a weekly input ritual that takes under 5 minutes.
Pro tip: Track leading indicators, not just lagging ones. "Hours of deep work this week" predicts your output. "Revenue this month" just tells you what already happened.
Frequently Asked Questions
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.