Productivity And Personal Organization Prompts

INPUTS
[goals]; [task list]; [appointments]; [available hours]; [energy patterns]

PROMPT
Act as a practical planning partner. Organize the week around the three outcomes that matter most, using the available hours and fixed commitments. Estimate task duration only as a labeled assumption and include buffer time. Break large tasks into visible next actions, group related work, and identify items to defer. Provide a weekly schedule and a short daily checklist. End with a Friday review that compares outcomes with the plan, identifies overload, and adjusts the following week without treating every unfinished task as failure.

INPUTS
[task list]; [deadlines]; [importance criteria]; [dependencies]; [capacity]

PROMPT
Triage this task list using the supplied priorities and capacity. Distinguish urgent commitments, important progress, routine maintenance, and optional work. Explain the ranking rather than relying on labels alone. Identify tasks that can be simplified, delegated, postponed, or removed. Produce an ordered list with a concrete next action, estimated effort range, and dependency for each priority item. Flag impossible deadlines and unclear obligations. Finish with a realistic plan for the next workday and a short message for renegotiating one overloaded commitment.

INPUTS
[task]; [desired output]; [time available]; [distractions]; [starting material]

PROMPT
Design a focused work session that ends with a concrete output. Clarify the smallest useful version of that output and divide the available time into preparation, concentrated work, and final review. Identify likely distractions and simple ways to reduce them. Give an opening checklist, a sequence of next actions, and a stopping rule to prevent unnecessary polishing. Include a fallback version if time runs short. End with a five-minute review that captures the result, remaining questions, and the next starting point.

INPUTS
[typical week]; [recurring tasks]; [tools]; [frustrations]; [goals]

PROMPT
Analyze the supplied workflow for avoidable friction, repeated decisions, duplicated effort, and tasks that do not support the goals. Distinguish workload problems from process problems. Recommend no more than five changes, each with a reason, setup effort, expected benefit, and way to evaluate it. Favor simple improvements that fit existing tools. Create a two-week trial plan and a review checklist. Do not assume that adopting more software improves productivity. End with one change to make today and one to postpone until the trial results are clear.

INPUTS
[email volume]; [work role]; [response expectations]; [tools]; [time budget]

PROMPT
Create an email processing routine that meets real obligations within the time budget. Define categories for action, waiting, reference, delegation, and deletion, with a clear rule for each. Suggest processing windows and an escalation path for genuinely urgent messages. Draft templates for acknowledgment, requesting missing information, and declining a nonessential request. Include a method for tracking commitments outside the inbox. Finish with a weekly cleanup checklist and a review metric that measures missed obligations and useful response time rather than inbox emptiness alone.

INPUTS
[desired habit]; [current routine]; [barriers]; [time]; [motivation]

PROMPT
Design a small habit experiment grounded in the user's existing routine. Define a specific action, reliable cue, minimum version, and simple record of completion. Identify likely barriers and create realistic fallback plans. Keep the initial commitment small enough to test for two weeks. Provide a daily tracking template and a weekly reflection. Avoid promises about automatic habit formation or fixed universal timelines. End with decision rules for expanding, simplifying, or replacing the habit based on what actually happened during the experiment.

INPUTS
[goal]; [deadline]; [resources]; [starting point]; [success definition]

PROMPT
Convert this goal into a manageable project. Define the finished outcome, intermediate milestones, dependencies, and tasks needed to reach them. Identify missing information and assumptions that affect scope. Create a work breakdown with a visible next action for each milestone and a realistic sequence based on resources. Include checkpoints that test progress before the final deadline. End with a minimum acceptable result, a contingency plan if time is reduced, and the first three actions to take today.

INPUTS
[recurring decisions]; [constraints]; [preferences]; [situations causing delay]

PROMPT
Help reduce unnecessary repeated decisions while preserving flexibility where judgment matters. Identify which choices can use defaults, simple rules, preparation, or batching. Propose a decision rule for each recurring situation and explain when an exception is appropriate. Avoid imposing preferences not present in the context. Deliver a short personal operating guide with examples and a two-week test. Finish with a review that checks whether the rules save effort, cause unintended problems, or need to be relaxed.

INPUTS
[goals]; [completed work]; [missed commitments]; [time use]; [lessons]

PROMPT
Guide a monthly review using the supplied record. Compare intended outcomes with actual results, identify meaningful progress, and examine why some commitments slipped. Separate controllable choices from external changes. Highlight activities that produced value and activities that consumed effort without advancing the goals. Create a concise review, three lessons, and next month's priorities with realistic measures. End with one commitment to stop, one to continue, and one to test. Avoid interpreting a busy month as automatically productive or unsuccessful.

INPUTS
[topics]; [sources]; [current notes]; [tools]; [retrieval needs]

PROMPT
Design a simple system for capturing and retrieving useful knowledge. Define what deserves a note, what can remain in the original source, and how to record source details. Create a note template with the key idea, context, evidence, application, and unresolved questions. Suggest a small tagging or linking approach that fits the existing tools. Include a weekly review and an example note based on supplied material. End with rules for avoiding duplicate notes and ensuring the system remains usable without excessive maintenance.