Create a practical personal productivity prompt pack for my work as [ROLE AND WORK CONTEXT]. My recurring work includes [RECURRING TASKS]. My current priorities and deadlines are [CURRENT PRIORITIES]. My communication audience is [AUDIENCE]. My constraints are [CONSTRAINTS]. Produce exactly six copy-and-paste prompts, each written in first person as if I am speaking to ChatGPT, Claude, Gemini, or Copilot. Make one prompt for each of these tasks: daily prioritization, weekly planning, meeting preparation, meeting follow-up, drafting a work message, and breaking a stalled project into next actions. Each prompt must contain its own square-bracket inputs that I can fill in. It must specify the output format and decision rules appropriate to the task. For example, prioritization should account for deadlines, impact, dependencies, and estimated effort; meeting preparation should distinguish decisions from updates; follow-up should assign an owner and due date only when supplied; project planning should identify dependencies and the smallest viable next step.
After each prompt, add a one-sentence “Use it when” explanation. Keep each prompt between 90 and 140 words and make the six prompts meaningfully different. Do not invent deadlines, commitments, stakeholder views, data, or completed work. Do not turn a task list into a schedule unless I provide available time. End with a “Prompt selection guide” that tells me which prompt to use for common situations such as too many tasks, an unclear project, or a meeting with no decisions. Before answering, check that each prompt creates a distinct deliverable and contains a concrete quality check. Check that none of the prompts assumes facts absent from its inputs. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [ROLE AND WORK CONTEXT] | Describe your role, work type, and the kind of decisions you make. | Operations manager at a 35-person software company; I coordinate launches, vendors, and internal processes. |
| [RECURRING TASKS] | List the work activities you repeat each week. | Weekly planning, vendor follow-ups, launch meetings, status updates, process documentation. |
| [CURRENT PRIORITIES] | List active goals, deadlines, and important dependencies. | Complete October onboarding update by October 10, choose a support vendor by October 18, and prepare a launch-readiness review. |
| [AUDIENCE] | Describe the people you usually communicate with. | Product, support, finance, external vendors, and the COO. |
| [CONSTRAINTS] | State time, approval, tool, workload, or communication constraints. | I have four hours of focus time each week; vendor decisions require finance approval; keep internal messages under 200 words. |
How to use
- Start with the task prompt that matches the artifact you need rather than using one large catch-all request.
- Paste current deadlines, dependencies, and constraints each time because they change the recommendation.
- Check proposed priorities against work that has a real due date, owner, or dependency.
- Follow up with: “Re-rank this plan assuming the vendor decision is blocked until finance replies on Thursday.”
Variations
Daily priority plan
Use this at the start of a day with competing work.
I need a plan for [AVAILABLE TIME] today. My tasks are [TASK LIST], with deadlines and dependencies in [CONTEXT]. Sort them into must do today, should do if time remains, delegate or defer, and waiting on others. For each must-do item, give the next physical action, estimated focus block, and reason for priority. Do not assume hidden urgency or schedule beyond my available time. Check that every must-do item has a stated deadline, impact, or dependency.
Meeting action recap
Use this after a meeting to turn notes into accountable follow-through.
Turn these meeting notes into a concise action recap: [NOTES]. Audience: [AUDIENCE]. Output decisions made, actions with owner and due date only where explicitly stated, open questions, and risks or dependencies. Separate commitments from discussion points. Draft a 120-word message that is ready to send, then list missing owners or dates for me to confirm. Do not invent agreement, deadlines, or stakeholder approval. Check that every action is traceable to the notes.
Project next steps
Use this when a project feels too large or has stopped moving.
Break [PROJECT] into the next 10 working actions using [CURRENT STATE], [GOAL], [DEADLINE], and [CONSTRAINTS]. Output a sequence with the smallest viable first action, owner if known, dependency, definition of done, and decision points. Identify work that can run in parallel and work that must wait. Do not invent scope, budget, approvals, or resources. Check that every action moves the stated goal forward and that no step hides an unresolved decision.
Tips
- Ask for a decision list after a meeting, not a summary alone; decisions and unresolved questions drive follow-through.
- When priorities conflict, give the model deadlines, consequences, dependencies, and effort estimates instead of a flat task list.
- Treat AI estimates as planning inputs, not commitments; adjust them using your own knowledge of interruptions and approval cycles.
- For messages, provide the recipient and the decision or action you need from them so the draft has a usable close.
FAQ
Can AI decide my priorities for me?
It can rank work from criteria you provide, but it cannot know unstated commitments or organizational context. Supply the tradeoffs that matter.
What is the most useful productivity prompt to start with?
Use a daily prioritization prompt when work is crowded, or a project-next-steps prompt when the problem is unclear scope rather than volume.
Should I paste confidential work into an AI tool?
Follow your organization’s approved-tool and data-handling rules. Remove sensitive customer, financial, personnel, and security details when required.