Name the result, time available and constraints. Ask for a short sequence of actions, then choose the first step you can actually complete.
Planning is useful when it reduces the decisions you need to make next. An elaborate plan that ignores your resources can make a simple task harder to start.
A practical workflow.
Describe the finish line
Explain what completed work would look like. Avoid a vague goal such as “be organised” when you can name a concrete result.
Set the boundaries
Include your time, budget, fixed commitments and relevant preferences. Explain which parts are flexible and which are not.
Ask for a small plan
Request a few actions in a sensible order, each with an output. Ask what can be removed if the available time is smaller than expected.
Start and update
Complete one action, record what you learned and adjust the remaining steps. Use the plan as a tool rather than a promise you must keep unchanged.
READY TO MAKE YOURS
Start with this prompt.
Help me plan this week around [commitments], [chores] and [available time]. Ask which items are fixed and what I would most like to finish. Make a simple daily plan with space for rest and a fallback for busy days. Keep estimates tentative and show what can move if plans change.
Replace the brackets. Leave out private details. Check the response.
ILLUSTRATIVE EXAMPLE
A clearer request.
A VAGUE STARTPlan my life.
A CLEARER BRIEFHelp me prepare for a move using three one-hour sessions this week. Prioritise actions that unblock later work and leave a short list of decisions I need to make.
The task and time limit make the plan usable.
Before you use the result.
- The goal is concrete.
- Actions fit available resources.
- Important dependencies come first.
- The plan can be adjusted after starting.
A few useful answers.
How detailed should my plan be?
Use enough detail to know what to do next. Add detail where uncertainty or coordination makes it useful, not simply to make the plan longer.
What if I keep postponing the first task?
Ask for a smaller version that takes ten minutes and produces one visible result. Then reconsider what made the original task difficult.
PUT THE GUIDE TO WORK
Planning prompts for a task you can actually finish
A useful plan answers a small question: what should I do next, with the time and materials I already have? Start with one outcome rather than a complete reinvention of your routine. These AI planning prompts help you turn a vague task into a finish line, check the order of the work and make a fallback before the week gets crowded.
Describe the result before the activities
“Sort out my paperwork” can mean finding a document, making a filing system or submitting an application. Those are different jobs. Write one sentence describing the result another person could recognise: “The application is submitted and the confirmation is saved.” Work backwards from that result. An activity belongs in the plan when it produces something the next activity needs. Colour-coding folders may feel productive, but it does not unblock an application if the missing item is a reference number. Ask the model to explain why each step is included, then remove steps with no clear contribution.
Plan around dependencies and real capacity
A dependency is something that must happen before another action can begin. You may need an answer from a landlord before booking a service, or a chosen topic before writing an outline. Put that question near the start. Capacity is the time you can genuinely use after fixed commitments, travel and breaks. If you have three short sessions, do not accept a plan with three full afternoons. Estimates are guesses until you try the work. Keep one small fallback that leaves a useful result even if a session is interrupted, such as a complete document list instead of a finished filing system.
Choose a review point, not a perfect schedule
Review after the first meaningful step. Ask what is complete, what turned out to be different and which dependency is still unresolved. Change the remaining plan using that information. A missed estimate is a reason to adjust the work, not to recreate the whole system. Keep the original finish line visible so the revision does not quietly grow the task. If the goal has changed, say so explicitly. A plan for preparing one room should not become a plan for renovating the entire house.
Open a card, copy the prompt and replace the brackets with your own details. Each card includes a follow-up and a check before you use the answer.
SITUATION 01 ↗
Turn a vague task into a finish line
Make the result clear before building a checklist.
Open the prompt +
Help me define this task: [task]. I want it done because [reason], and I have [available time]. Ask up to three questions that would change the plan. Then propose two concrete finish lines: a minimum useful version and a fuller version. Explain what is outside each version. Do not assume I can buy equipment or delegate work.
Refine the next draft
I choose [version]. Rewrite it as one sentence with a visible completion check. Remove any activity that is useful but unnecessary for that result.
Before you use it
Choose the version yourself. Check that completing the task will solve the actual problem, rather than just produce a tidy checklist.
SITUATION 02 ↗
Find the step that unlocks the rest
Avoid working on something that is waiting for a decision.
Open the prompt +
My finish line is [result]. Here are the steps I think I need: [steps]. These questions are unanswered: [questions]. Put the steps in a dependency order. For each one, show what must be true before it starts and the output it creates. Mark uncertain dependencies as questions. Identify the earliest action I can complete without waiting for someone else.
Refine the next draft
Which parts can happen independently? Give me one small action to take while I wait for [reply or decision], without pretending that the blocked work is finished.
Before you use it
Confirm external deadlines, appointments and requirements with the actual organisation or person involved. The model cannot confirm availability for you.
SITUATION 03 ↗
Fit the work into three real sessions
Use your available time instead of an imaginary free day.
Open the prompt +
Plan [task] in these three sessions: [session lengths and dates]. The important result is [result]. I already have [materials], and these limits are fixed: [limits]. Give each session one main action and a concrete output. Label time estimates as tentative. Include a fallback if one session is lost, and show what I should deliberately postpone.
Refine the next draft
The first session took [actual time] and produced [output]. Revise only the remaining sessions. Keep the finish line unchanged and explain the trade-off if the full version no longer fits.
Before you use it
Leave room for preparation, stopping and unavoidable interruptions. A short plan is useful only if its actions fit the time you really have.
SITUATION 04 ↗
Restart a plan that slipped
Recover the useful next step without doubling tomorrow’s workload.
Open the prompt +
This plan slipped: [original plan]. I completed [actual completed work]. I now have [new available time]. Help me recover a minimum useful result. Separate essential remaining steps, steps that can wait and assumptions to confirm. Suggest the next action I can finish in [small time block]. Do not schedule every missed task into the next day.
Refine the next draft
I completed [next action]. What is the smallest remaining sequence that reaches [finish line]? Keep completed work out of the new checklist.
Before you use it
Use a realistic finish line. If a deadline cannot be met, make the needed communication a separate action rather than concealing the delay in the plan.
The examples below are original, illustrative edits using fictional situations. They show the checks to make, rather than promising what an AI tool will produce.
Your one-task planning sheet
Finish line: [one observable result] Why it matters now: [reason] Fixed commitments: [times / obligations] Available sessions: [length of each session] Materials already available: [items] Decisions or replies needed first: [dependencies] First action and its output: [action → result] Next action it enables: [action] Minimum useful fallback: [smaller result] Review after: [specific step] What I will leave out: [scope boundary]
WORKED EXAMPLE
Replace “get organised” with a usable sequence
An original fictional example: Alex has two 30-minute sessions to prepare an application, but does not know which documents are required.
FIRST DRAFTSession 1: Create a colour-coded filing system.
Session 2: Collect every document and submit the application.
AFTER CHECKINGSession 1: Read the actual application instructions. Make a required-document list and identify anything missing.
Between sessions: Request the missing document if necessary.
Session 2: Prepare the documents already available. Submit only if all requirements are met; otherwise record the remaining dependency.
What changed
The revision puts the unknown requirement before the organisation task. It does not promise that a third party will supply a document within the two sessions. The useful fallback is a complete requirement list and a specific request.
WORKED EXAMPLE
Keep a small household task small
An original fictional example: Sam wants one shelf cleared before a guest arrives and has 25 minutes.
FIRST DRAFTDeep-clean the room, buy storage boxes, organise every cupboard and redesign the shelf.
AFTER CHECKINGClear the shelf surface into a temporary sorting space. Return the items that belong there. Put items belonging elsewhere into one labelled container to sort later. Stop when the shelf is usable; leave the cupboards for another task.
What changed
The result is a usable shelf within a narrow task. Buying equipment and reorganising cupboards do not belong to this finish line. The temporary container is a conscious fallback, not a claim that the whole room is organised.
Try it with your own task.
Choose one task that has been sitting on your list. Write its finish line, then use the dependency prompt before making a schedule. Try the first action and record how long it actually took; use that observation to revise the rest.
