Create a minimum viable plan for low energy

Author: AILesson5 min setupTested with:ChatGPTReviewed: 2026-08-28

Quick answer

Protect essential commitments with smaller actions, explicit limits, and recovery-aware choices. Provide: Current capacity, Tasks and commitments, Flexibility and support. Expected result: A gentle today plan with must-do work, stop rules, communication, and a restart point.

1

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

2

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Create a minimum viable plan for the stated low-capacity period. This is workload planning, not medical diagnosis.

Current capacity, time, concentration, constraints, and safety concerns:
[state]

Tasks, true deadlines, consequences, affected people, and promises:
[commitments]

Flexibility, minimum outputs, contacts, breaks, and support:
[support]

Do not infer why energy is low. If the input describes immediate danger, severe symptoms, or inability to stay safe, pause ordinary planning and recommend appropriate urgent human help. Otherwise distinguish hard commitments from preferences and self-imposed targets. Protect food, medication instructions already provided by a professional, rest, safety, and essential care. Never suggest concealing missed work.

Build three capacity levels: minimum, if-energy-improves, and stop-for-today. Use actions small enough to start, with time boxes, a clear done condition, and no hidden follow-up. Identify what to defer, simplify, ask help with, or communicate—without sending or cancelling anything. Include a short honest message where needed, a break plan, warning signs to stop, tomorrow's restart cue, and assumptions requiring confirmation. Keep the total within supplied time and show the arithmetic.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Current capacity
It is 14:00. I have about 90 minutes of usable concentration before school pickup at 16:00 and rate energy 3/10. I can do short reading/editing but not a complex analysis. No immediate safety concern. I need a 10-minute snack break.
Tasks and commitments
Client draft promised today; it has 800 words and needs a factual pass, but the optional design examples are unfinished. Expense form is due Friday. Team chat has two non-urgent questions. At 15:30 I must leave for pickup. I planned an online course lesson for myself.
Flexibility and support
Client said a text-only draft is acceptable for review. Colleague Mei can check links tomorrow. I may move the course and expense form. If needed I can tell the client examples will follow tomorrow. I want 15 minutes after work with no screen.

Example output

Available window is 90 minutes of concentration, ending before the 15:30 departure. Minimum plan totals 75 minutes: 10-minute snack away from screen; 5 minutes to open the draft and mark only factual claims; two 20-minute factual-review blocks with a 5-minute pause; 10 minutes to make the text readable and label unfinished examples; 5 minutes to prepare the client message. Done means the 800 words have been checked against available sources, uncertain claims are marked, and the text-only review draft is ready—not that optional examples are complete. Keep the final 15 minutes unscheduled as transition/buffer.

Suggested message, not sent: “I have the text-only draft ready for review today as agreed. The optional design examples are not included yet; I can add them tomorrow after link review. Please let me know if that changes what you need for this round.” Ask Mei tomorrow rather than assigning her without confirmation.

If energy improves after the second block, use at most 10 buffer minutes to answer one chat question; otherwise leave both unread or acknowledge tomorrow. Defer the Friday expense form and personal course explicitly to tomorrow's list. Stop for today if accuracy declines, the same paragraph is reread three times, or departure preparation must start. Restart cue tomorrow: open the marked example section, confirm Mei's availability, then schedule one 25-minute block. No medical cause is inferred.

Why this works

  1. 1

    Capacity levels prevent an all-or-nothing plan from turning a difficult day into a larger backlog

  2. 2

    Explicit communication protects trust when the original commitment no longer fits available capacity

Check the result

  • Does the minimum plan fit the stated time and preserve essential care and safety

  • Does every action have a small start, time box, and done condition

  • Are deferrals and messages suggestions rather than actions falsely presented as completed

Use it with confidence

Frequently asked questions

Practical answers about when to use this recipe, what to provide, and where human review still matters

What should I prepare before using “Create a minimum viable plan for low energy”?

For “Create a minimum viable plan for low energy,” prepare Current capacity, Tasks and commitments, and Flexibility and support. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Create a minimum viable plan for low energy” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A gentle today plan with must-do work, stop rules, communication, and a restart point—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Create a minimum viable plan for low energy”?

The published test record for “Create a minimum viable plan for low energy” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

More ways to explore

Where this recipe fits

Keep the work moving