Plan a Saturday, a 4-day trip, and dinner from what's in the fridge

Most household planning fails in the same three places. The Saturday you meant to enjoy turns into four stops, a missed nap and a meltdown in a parking lot. The trip you spent weeks researching leaves everyone needing a day off when they get home. And at six in the evening on a Wednesday, the fridge has eleven things in it and none of them are dinner.

This guide has three prompts for those three jobs. They come from the chapter on domestic logistics in the book Stop Typing, Start Asking and are reproduced here exactly. Around each one you get the situation it fits, what to put in the square brackets, what a usable answer looks like, and how to tell when the chatbot quietly ignored you.

They all work the same way, and it is worth saying up front: the plan does not get good because the chatbot knows your town. It gets good because you name the things that cannot move — the nap, the walking limit, the thirty-five minutes — and then cap how much can be squeezed around them. The constraints are the product. Everything else is filling.

Why 'plan our weekend' comes back useless

Ask any free chatbot to plan a fun Saturday for your family and you will get something like this: nine o'clock at the science museum, eleven at the zoo, lunch downtown, the botanical garden at two, ice cream at four. It reads beautifully. It is also five stops, three drives through the middle of a city, no nap, no parking, and no acknowledgement that getting two small children out of a car takes ten minutes each way.

The one-line request leaves out everything that makes the day hard. It does not say when you actually get out the door, what time the toddler stops being a person, how long you are willing to drive, or how much gear has to be loaded and unloaded at every stop. With none of that, the chatbot optimises for interesting places, because interesting places are what a good day looks like when nobody has mentioned logistics.

The three prompts below all fix this the same way. They list the fixed points as labelled fields, they cap the number of things you are allowed to do, and they force the plan to include the dead time between them. The cap is the line that does the most work, and it is the line people are most tempted to delete.

A Saturday that survives the 1 p.m. nap

The situation: one day, small children, and a window of usable hours that is much shorter than the calendar suggests. You do not need more options. You need a sequence that fits, with somewhere to go when the playground turns out to be full.

Two lines carry this prompt. The pacing rule caps you at two public stops and makes the chatbot schedule twenty-minute buffers around every drive, which is the part you would never write down yourself and the part that always breaks the day. The contingency requirement is the other one: every stop comes with a fallback, so a crowded car park or a sudden downpour changes one block instead of ending the outing.

Act as a practical family logistics coordinator. Create a realistic, low-stress weekend day itinerary based on the following constraints:

- Location: [City/Neighborhood, e.g., North suburbs of Austin, TX]
- Party: [Number of adults and ages of children, e.g., 2 adults, 1 child aged 4, 1 child aged 18 months]
- Time Window: [Start time] to [End time, e.g., 8:30 AM to 5:00 PM]
- Fixed Anchors (Non-negotiable):
  * Nap/Rest Time: [e.g., 1:00 PM – 3:00 PM at home]
  * Meal Requirements: [e.g., Casual lunch at 11:45 AM, kid-friendly with high chairs and quick service]
- Budget: [e.g., Under $50 total, free outdoor options preferred]
- Maximum Travel Radius: [e.g., Within 20 minutes drive of home]
- Pacing Rule: Maximum of 2 public activity stops. Include 20-minute buffer periods between all driving transitions for loading/unloading gear.

Format the response as a chronological, time-blocked schedule. For each stop, list:
1. Exact time block
2. Activity name and realistic duration
3. Parking/logistics note
4. Built-in contingency option if the venue is crowded or weather turns bad.

Fill Location with a neighbourhood and a metro area, not just a city, because a twenty-minute radius means something completely different on two sides of the same town. Party needs exact ages — eighteen months and four years are not the same child, and the difference decides whether you need a stroller, a changing table and a hard nap window. Set the time window to when you will genuinely be in the car, not when you hope to be. Then treat Fixed Anchors as literally non-negotiable: name the nap hours and the lunch time, and put lunch earlier than feels natural, because a queue at half past twelve with a hungry toddler is the most common way one of these days collapses. Give the travel radius in minutes rather than distance.

What comes back is a chronological schedule with two real stops, a parking note for each, and driving blocks that look wastefully long. They are not wasteful — that is the loading, the shoes, the last-minute nappy change. Sanity-check it by adding the blocks up: if the drive is ten minutes and the plan reserves forty-five for the transition, the prompt did its job. Every venue name it gives you is a placeholder to verify, not a recommendation.

A four-day trip with two things a day

The situation: a trip with a group whose pace is set by its slowest member — a grandparent who cannot manage long standing queues, a teenager who cannot manage a slow morning, and you in the middle trying to make the days fit both. The default itinerary a chatbot writes for a destination assumes one fit adult with no opinions.

Three constraints in this prompt change the shape of the result. Two primary attractions a day is the ceiling. Keeping them in the same geographic quadrant is what removes the hour of transit nobody budgets for. And the mandatory ninety-minute unscheduled block in the afternoon is the only part of the itinerary that makes the rest of it survivable, because it is where the day absorbs a late lunch, a long queue or a nap without falling apart.

The dinner rule matters more than it looks. Requiring dinner near your base or near the last afternoon stop stops the plan from sending you back across town at seven in the evening, which is the point at which most well-researched trips turn into an argument.

Act as a travel operations planner. Build a balanced, realistic [Number of Days]-day itinerary for a trip to [Destination] with the following constraints:

- Group Profile: [e.g., 2 adults, 1 senior with limited walking stamina, 1 teenager]
- Trip Dates/Season: [e.g., Mid-October, 4 full days]
- Accommodation Base: [e.g., Hotel in Central District]
- Transportation Method: [e.g., Public transit / Walking / Rental Car]
- Daily Rhythm Constraints:
  * Maximum 2 primary attractions per day, located in the same geographic quadrant to minimize transit.
  * Mandatory 90-minute mid-afternoon unscheduled buffer block for resting, coffee, or spontaneous exploring.
  * Dinner must be near the accommodation base or the final afternoon stop.
- Mobility/Pacing Restrictions: [e.g., Maximum 8,000 steps per day; avoid steep stairs or long standing lines]

Format the output as a Markdown table summarizing the daily plan, followed by day-by-day bulleted itineraries including transportation routes, rest pauses, and reservation deadlines.

Write the Group Profile around the limiting person and say what the limit is, not just their age: limited walking stamina, uses a cane on stairs, cannot stand in queues. Give dates and season, because season decides daylight, heat and what is closed. Accommodation Base should be a district rather than a hotel name, since the district is what the routing actually depends on. Pick one primary transport method rather than listing three. Then put a number in the mobility line — a daily step ceiling plus the specific things to avoid — because a number changes the plan and an adjective does not.

You should get a summary table of the days followed by day-by-day detail with routes, rest pauses and reservation deadlines. Check three things before you book anything. Open a map and confirm the two attractions in each day really are close together. Treat every reservation deadline as a guess and verify it on the venue's own booking page. And look for the ninety-minute block in every single day — it is the first thing that drifts, and it usually disappears by day three under something that sounds unmissable.

Dinner from what is already in the fridge

The situation: it is early evening, you are not going to the shop, and you want dinner out of what exists. Ask the usual way — what can I make with chicken and rice — and you get a recipe requiring stock, garlic cloves and half a lemon, which is a shopping list dressed as an answer.

This prompt closes that door twice. It bans any major ingredient outside your list, and it limits pantry staples to a short set that you fill in yourself, so the chatbot cannot assume butter, onions or a spice rack. The cookware rule is the other half: one pan, one pot or one sheet, because on a weeknight the washing-up is the reason people order in.

Act as a pragmatic home chef and inventory coordinator. Generate [Number, e.g., 3] distinct dinner meal recipes using strictly the ingredients listed below.

Rules:
1. Do NOT assume or add any major ingredients outside of this list.
2. Standard basic pantry staples are permitted ONLY from this list: salt, black pepper, olive oil, vegetable oil, water, and [list any 2-3 spices you know you have, e.g., garlic powder, soy sauce].
3. Active preparation and cooking time must be under 35 minutes per meal.
4. Minimize dirty cookware (prefer one-pan, sheet-pan, or one-pot meals).

Available Ingredients:
- Proteins: [e.g., 2 cans black beans, 3 eggs, 1 half-block cheddar cheese, 1/2 pound frozen ground turkey]
- Vegetables: [e.g., 3 carrots, 1/2 bag frozen peas, 1 yellow onion, 2 soft tomatoes]
- Starches/Grains: [e.g., 1 cup white rice, half-box elbow macaroni, 4 corn tortillas]
- Sauces/Condiments: [e.g., Mayo, salsa, mustard]

Format the output for each meal with:
- Meal Name
- Cookware required (e.g., Single skillet)
- Prep time & Cook time
- Step-by-step instructions (under 5 numbered steps)
- Ingredients utilized from the list.

List ingredients with quantities and condition, in the four groups the prompt gives. Half a block of cheddar, two soft tomatoes, half a bag of frozen peas. Say frozen when something is frozen — it is the single detail that decides whether a thirty-five-minute meal is possible at all, since thawing eats the whole budget. In the staples line, name only the two or three spices and sauces you have actually got. The temptation is to pad that list to get nicer recipes, and padding it is exactly how you end up halfway through step three without the thing step three needs.

Expect three distinct meals, each with the cookware named, prep and cook time stated separately, under five steps, and a list of which of your ingredients it used. Audit that last list — it is there so you can. Cross items off as the meals claim them and you will catch the common failure, where the same half onion is spent in all three recipes. Then scan the steps for anything that was never on your list; butter, garlic cloves, stock and citrus are the usual intruders. If one appears, say which ingredient was not on the list and ask for that meal again.

The two-minute check before you commit

Treat every proper noun in the answer as a guess. A chatbot writing about your neighbourhood produces plausible place names, some of which are real, some of which closed two years ago, and some of which have a splash pad that runs for four months of the year. The plan's structure is the useful part; the specific venues are a shortlist to check.

Then check the arithmetic. Add the time blocks and see whether the day ends when you said it ends. Count the stops against the cap you set. Count the steps against the walking limit. These are the instructions that get dropped most often, and they get dropped silently.

When something is wrong, hand the correction back rather than editing by hand. One line — the drive is twenty-five minutes, not ten, re-time the day — gets the whole schedule refitted, including the buffers you would have forgotten to adjust. And keep the filled-in prompt somewhere. Next weekend you change three fields instead of starting over, which is the point at which this stops being a novelty and starts saving you the Friday evening you usually lose to it.

What this cannot do

• It does not know what is actually near you. Venue names, opening hours, seasonal closures and whether a place still exists are all outside what a chatbot can verify. Use the structure, then confirm each stop yourself before anyone gets in the car.
• It cannot see availability, tickets or costs. The budget line shapes the kind of plan you get, but any figure in the answer is an estimate, and reservation deadlines are invented. Check them on the booking page that actually sells the ticket.
• It cannot judge terrain or real travel time. A route that looks short on paper can be a steep hill, a station with no lift, or gravel a stroller will not cross. Stated travel times are approximations, and the mobility limit you set is respected in spirit rather than measured.
• It is not a food-safety or allergy check. It will build a meal around something that has been in the fridge longer than it should have been, and it does not know what anyone at the table cannot eat. State allergies and restrictions in the prompt, and still decide for yourself what is safe to cook and safe to eat.
• It cannot fix a day that does not fit. Give it five fixed anchors inside four hours and it will still hand you a tidy schedule, because producing a schedule is what it does. Conflicts get smoothed over rather than flagged. Cutting something is your job.
• It will drift past the rules you set. A third stop, a missing buffer, an ingredient you never listed, the afternoon rest block quietly filled. Count the stops, the words and the ingredients before you trust the plan, and regenerate rather than patching it yourself.

Related reading

• Stop Typing, Start Asking — full first chapter, free, no email required
• Full contents and what is included
• How to repurpose one long-form video into 20 posts
• The three emails you keep putting off, each under 120 words
• All Avalon Store products