Productivity & Planning prompts

Converts a single goal and deadline into a structured week-by-week task plan; ideal for launching a new project or personal initiative.

I have the following goal: [GOAL]. My deadline is [DEADLINE]. I can dedicate approximately [HOURS_PER_WEEK] hours per week to this. Break this goal down into a concrete weekly action plan, listing specific tasks for each week between now and the deadline. Present the plan as a numbered week-by-week list, and flag any weeks where the workload is especially heavy.

How to use: Fill in your goal precisely — the more specific it is, the more actionable the output will be.

Turns a raw to-do list into a time-blocked daily schedule; great for overwhelming mornings when you're not sure where to start.

Here is my to-do list for today:
[PASTE_TODO_LIST]

My working hours are [START_TIME] to [END_TIME]. I have the following fixed commitments today: [FIXED_COMMITMENTS]. Arrange these tasks into a realistic hour-by-hour schedule, grouping similar tasks where helpful and building in short breaks. Flag any tasks that probably won't fit and suggest what to defer.

How to use: Paste your actual to-do list as a bullet list and include any meetings or appointments in the fixed commitments field.

Produces a tailored kickoff checklist to ensure nothing is missed when launching a new project; useful for project managers and team leads.

I am about to start a project with the following description: [PROJECT_DESCRIPTION]. The team involved includes: [TEAM_ROLES]. Generate a comprehensive project kickoff checklist covering: defining scope, aligning stakeholders, setting milestones, establishing communication norms, identifying risks, and any domain-specific items relevant to this type of project. Format it as a checklist with checkboxes and brief explanations for each item.

How to use: Be specific about the project type (e.g., software launch, marketing campaign) so the checklist includes domain-relevant items.

Sorts a messy backlog into clear priority quadrants so you can focus on what truly matters; great for weekly reviews.

Here is my current task backlog:
[PASTE_TASK_LIST]

Using the Eisenhower Matrix, categorize every task into one of four quadrants: (1) Urgent & Important — do now, (2) Not Urgent & Important — schedule, (3) Urgent & Not Important — delegate or minimize, (4) Not Urgent & Not Important — eliminate. Present the output as a clearly labeled table with one row per task and a one-line rationale for each placement.

How to use: Include all tasks, even small ones — the matrix is most useful when you're not pre-filtering.

Transforms fuzzy ambitions into well-formed SMART goals with immediate next steps; useful at the start of any planning session.

I have the following vague intention: '[VAGUE_INTENTION]'. Rewrite it as a SMART goal — Specific, Measurable, Achievable, Relevant, and Time-bound. Then, beneath the SMART goal, list three concrete first actions I could take this week to make progress toward it. Keep the tone practical and direct.

How to use: The vaguer and more honest your intention, the more useful the rewrite — don't polish it before pasting.

Guides you through a reflective weekly review conversation and ends with a synthesized action plan; ideal as a Friday or Sunday ritual.

Help me conduct a structured weekly review. Here is a brief summary of what happened this week: [WEEK_SUMMARY]. My top goals for the month are: [MONTHLY_GOALS]. Ask me the following questions one by one and wait for my answer before moving to the next: (1) What did I complete this week that I'm proud of? (2) What did I leave undone, and why? (3) What patterns or blockers keep recurring? (4) What are my three most important tasks for next week? (5) What do I need to say no to or reschedule? After I answer all five, synthesize a one-paragraph weekly recap and a clean next-week task list.

How to use: Treat this as a real dialogue — answer each question honestly before asking for the next one.

Creates a phased 90-day ramp-up plan for someone starting a new role; perfect for professionals who want to make a strong early impression.

I am starting a new role as [JOB_TITLE] at a [COMPANY_TYPE] company. My key responsibilities are: [RESPONSIBILITIES]. Design a structured 90-day onboarding and ramp-up plan divided into three phases: (1) Learn — days 1–30, (2) Contribute — days 31–60, (3) Lead — days 61–90. For each phase, include: the primary focus, three to five specific weekly objectives, key relationships to build, and metrics or signals that would indicate success. Format as clearly labeled sections.

How to use: Include nuanced responsibilities — generic titles produce generic plans, so specificity pays off here.

Audits an existing schedule against project demands and proposes a conflict-free revision; useful before a busy period.

Here is my schedule for the upcoming [TIME_PERIOD]:
[PASTE_SCHEDULE]

Here are the projects and their deadlines I need to make progress on:
[PASTE_PROJECTS_AND_DEADLINES]

Analyze the schedule for conflicts, overloads, and gaps. Then propose specific changes — reschedules, time blocks, or deferrals — to make the schedule realistic. Present your analysis first, then a revised schedule as a clean table.

How to use: Paste the schedule in any format — bullet list, table, or plain text — the model will parse it.

Surfaces hidden risks in a project plan before execution begins; ideal for high-stakes projects where failure is costly.

Here is my project plan:
[PASTE_PROJECT_PLAN]

Conduct a pre-mortem: imagine it is [DEADLINE] and the project has failed badly. Generate a list of the ten most plausible reasons it failed, ordered from most to least likely. For each failure mode, suggest one concrete mitigation action I can take now. Present the output as a numbered table with three columns: Failure Mode | Likelihood Rationale | Mitigation Action.

How to use: Be honest about constraints and dependencies in the project plan — sugarcoating it reduces the pre-mortem's value.

Transforms raw meeting notes into a structured action-item table with owners and due dates; saves time after every meeting.

Here are the raw notes from a meeting:
[PASTE_MEETING_NOTES]

Extract and structure all action items from these notes. For each action item, identify: (1) the task, (2) the owner (use 'TBD' if unclear), (3) the due date (use 'Not specified' if not mentioned), and (4) any dependencies. Format as a clean table. After the table, list any open questions or decisions that were left unresolved.

How to use: Paste notes verbatim — messy, unedited notes work fine and often produce better extractions.

Creates a personalized time-audit system so you can see exactly where your hours are going; useful before redesigning your schedule.

I want to audit how I spend my time at work. My job title is [JOB_TITLE] and my main responsibilities are: [RESPONSIBILITIES]. Design a time-audit tracking template I can use for one week. Include: a categorized list of activity types relevant to my role, a simple daily logging format, and five reflection questions I should answer at the end of the week to identify time-wasters and optimization opportunities.

How to use: Adapt the activity categories after the first day if your actual work doesn't match them.

Produces a structured stakeholder communication plan to keep everyone appropriately informed; essential for multi-party projects.

I am managing a project with the following details: [PROJECT_DESCRIPTION]. The stakeholders involved are: [LIST_OF_STAKEHOLDERS_AND_ROLES]. Create a stakeholder communication plan covering the project timeline of [TIMELINE]. For each stakeholder group, specify: communication frequency, preferred format (e.g., status email, meeting, dashboard), key information to share, and who is responsible for sending it. Format as a table, then add a brief narrative summary of the overall communication strategy.

How to use: List stakeholders with their roles and influence level so the plan can be calibrated to their needs.

Creates a multi-level Work Breakdown Structure for a complex project, including critical-path identification; ideal for formal project planning.

Here is my project goal: [PROJECT_GOAL]. The final deliverable is: [DELIVERABLE]. Break this down into a full Work Breakdown Structure (WBS) with at least three levels: (1) major phases, (2) deliverables within each phase, (3) specific tasks required to produce each deliverable. Format as an indented outline. After the WBS, provide a brief critical-path note identifying which tasks are likely to be on the critical path and why.

How to use: The more precisely you define the final deliverable, the more accurate and useful the WBS will be.

Drafts a full OKR set aligned to an annual goal, with confidence ratings for calibration; ideal for quarterly planning sessions.

I am planning OKRs for [TEAM_OR_INDIVIDUAL] for [QUARTER_AND_YEAR]. Our broader annual goal is: [ANNUAL_GOAL]. Current context and constraints: [CONTEXT]. Draft three Objectives, each with three to four Key Results. Each Objective should be inspirational and qualitative; each Key Result should be measurable and time-bound. After the OKRs, add a short 'confidence check' for each Key Result, rating it 1–3 (1 = stretch, 2 = realistic, 3 = conservative) with one line of reasoning.

How to use: Provide honest context about what's realistic — the confidence check is only useful if the OKRs aren't all conservatively set.

Identifies delegation and automation opportunities in an overloaded task list; essential when a leader is a bottleneck.

Here is a list of all the tasks and responsibilities I currently own:
[PASTE_FULL_TASK_LIST]

My role is [YOUR_ROLE] and I manage or work alongside the following people: [TEAM_MEMBERS_AND_SKILLS]. I need to free up approximately [HOURS_PER_WEEK] hours per week. Analyze the list and recommend: (1) tasks to delegate immediately with the suggested person and a handover note, (2) tasks to automate or streamline, (3) tasks only I can do. Explain your reasoning for each recommendation.

How to use: Be honest about which tasks you're holding onto out of habit versus necessity — include those too.

Drafts a personal productivity policy you can actually commit to; useful for anyone who wants clearer self-management defaults.

I want to write a personal 'productivity policy' — a short document of rules and defaults I commit to in order to do my best work. My role is [ROLE], my biggest productivity challenges are [CHALLENGES], and my core work values are [VALUES]. Draft a one-page productivity policy that includes: (1) my working hours and deep-work blocks, (2) communication response norms, (3) meeting rules, (4) task and priority system, and (5) a weekly and daily reset routine. Write it in first person as if I am the author.

How to use: List your genuine challenges — not aspirational ones — so the policy addresses real friction points.

Structures a single deep-work session from setup to debrief so you enter and exit with intention; ideal before tackling a hard creative or analytical task.

I want to have a highly productive deep-work session today focused on: [TASK_OR_PROJECT]. I have [DURATION] available. My typical distractions are: [DISTRACTIONS]. Design a session plan that includes: (1) a two-minute pre-session intention-setting prompt, (2) a distraction elimination checklist, (3) the specific output or milestone I should aim to hit by the end, (4) a time-block breakdown for the session, and (5) a two-minute post-session debrief prompt.

How to use: Be specific about the task — 'write report introduction' beats 'work on report'.

Surfaces hidden inter-team dependencies and coordination risks in a complex project; valuable for program managers and engineering leads.

Here is a description of our multi-team project:
[PROJECT_DESCRIPTION]

The teams and their responsibilities are:
[TEAM_LIST_AND_RESPONSIBILITIES]

Analyze this and produce: (1) a dependency map listing every team-to-team dependency, specifying which team is the blocker and which is the dependent, (2) a risk assessment for each dependency, and (3) a recommended coordination cadence to prevent bottlenecks. Format the dependency map as a table and the risk assessment as a separate numbered list.

How to use: List all teams even if their role seems minor — minor dependencies often become major blockers.

Designs a minimal but complete habit-tracking and accountability system tailored to your lifestyle; for anyone building new routines.

I want to build the following habits: [LIST_OF_HABITS]. My schedule and lifestyle context: [CONTEXT]. Design a practical habit-tracking system for me that includes: (1) a daily tracker template, (2) suggested times or triggers for each habit based on my context, (3) a weekly review question to assess each habit, and (4) a simple rule for what to do when I miss a day. Keep everything minimal — I want something I'll actually use.

How to use: Limit habits to five or fewer for the first iteration — the system works best when it isn't overwhelming.

Produces a formal scope statement that sets boundaries and prevents scope creep; essential at the start of any defined project.

I am leading a project with the following goal: [PROJECT_GOAL]. The requesting stakeholder is [STAKEHOLDER] and the team delivering it is [DELIVERY_TEAM]. Draft a formal project scope statement that includes: (1) project purpose and justification, (2) in-scope deliverables with acceptance criteria, (3) explicitly out-of-scope items, (4) assumptions, (5) constraints, and (6) a change-control note explaining what happens when scope changes are requested. Write in clear, professional language suitable for stakeholder sign-off.

How to use: The 'out-of-scope' section is the most important — think about what people might naturally assume is included but isn't.

Structures a raw brainstorm into a prioritized roadmap with clear horizons; ideal after a team ideation session.

Here is a raw brainstorm of ideas, features, and initiatives for [CONTEXT]:
[PASTE_BRAINSTORM]

Organize these into a prioritized roadmap using the following criteria: (1) impact on [PRIMARY_GOAL], (2) estimated effort (low / medium / high), (3) dependencies on other items. Group items into three roadmap horizons: Now (next 30 days), Next (31–90 days), Later (90+ days). Present as a table with columns: Item | Impact | Effort | Dependencies | Horizon. Add a short narrative explaining the top three items chosen for 'Now'.

How to use: Paste ideas without pre-filtering — the model will do the sorting, and raw input often reveals more value.

Converts raw project notes into a polished, structured status report for stakeholders; saves significant time on recurring reporting.

I need to write a project status report. Here are the raw notes and updates from this reporting period:
[PASTE_RAW_NOTES]

The project is: [PROJECT_NAME]. The audience is: [AUDIENCE]. Format the report with these sections: (1) Executive Summary (3 sentences max), (2) Progress This Period, (3) Planned vs. Actual milestones table, (4) Risks and Issues, (5) Next Period Priorities. Use a professional but concise tone. Highlight anything that needs a decision or action from the reader.

How to use: The rawer and more honest your notes, the more useful the report — include setbacks, not just wins.

Creates a full agenda and reflection prompts for a solo quarterly planning retreat; ideal for professionals who want intentional quarterly direction.

I want to run a solo quarterly planning retreat for [DURATION] on [DATE_OR_TIMEFRAME]. My role is [ROLE] and I am planning for [QUARTER]. Design a structured agenda for the retreat that covers: reviewing the past quarter (wins, misses, lessons), assessing current priorities and commitments, setting goals and intentions for the next quarter, identifying projects to start, stop, or continue, and ending with a concrete 90-day plan. Include time allocations, reflection prompts for each section, and a recommended pre-retreat preparation checklist.

How to use: Choose a date when you can genuinely disconnect — the agenda is only as good as the focus you bring to it.

Applies Pareto analysis to your role to surface the highest-leverage activities; useful for productivity audits and role redesign.

Here is a description of my role and typical week: [ROLE_AND_WEEK_DESCRIPTION]. My primary performance goals are: [PERFORMANCE_GOALS]. Apply the 80/20 principle to analyze my activities: identify the roughly 20% of tasks or activities most likely to drive 80% of my results toward my goals. Then identify the low-value activities that consume time without proportionate return. Present findings as two lists — High-Leverage Activities and Low-Value Activities — with a one-line rationale for each item, followed by three specific recommendations for restructuring my week.

How to use: Describe your typical week honestly, including meetings and admin — not just the ideal version of your week.

Produces a decision log template and usage protocol to preserve institutional knowledge; invaluable on projects with many stakeholders or frequent changes.

I am managing a project called [PROJECT_NAME] with a team of [TEAM_SIZE] people. We frequently lose track of decisions and the reasoning behind them. Design a decision log template suitable for our project. Include: fields to capture in each entry, guidance on what qualifies as a decision worth logging, a short protocol for how and when to update it, and an example entry using this fictional decision: 'We decided to use a phased rollout instead of a big-bang launch.' Explain how this log prevents common project problems.

How to use: Customize the fields after the first week based on which information your team actually references.

Analyzes resource capacity against a project plan and recommends conflict resolutions; critical for projects where people are the constraint.

Here is my project plan: [PASTE_PROJECT_PLAN]. My available resources are: [AVAILABLE_RESOURCES_AND_CAPACITY]. The project must be delivered by [DEADLINE]. Analyze whether the current resources are sufficient to meet the deadline. Produce: (1) a resource allocation table showing who does what and when, (2) identification of any resource bottlenecks or overloads, (3) options for resolving each conflict (e.g., resequencing tasks, reducing scope, adding resource), and (4) a recommended resolution for each conflict with trade-off notes.

How to use: Include real capacity numbers (e.g., person is 50% allocated elsewhere) — assumed full availability leads to unrealistic plans.