Most people ask ChatGPT for a how-to and get a clean numbered list. This approach asks for the same list, plus a map of where you’ll get stuck. It takes one extra paragraph.
The idea comes from u/Ok_Negotiation_2587 on r/ChatGPTPromptGenius. It’s simple, and it fixes something that annoys almost everyone who uses AI for instructions.
The key idea
Ask for steps to set up a printer, write a spreadsheet formula, fill in a tax form or configure a router. You get a tidy list that works great if you already know what you’re doing.
The gap is always the same. The list tells you what to do. It never tells you what you should be seeing. So when step 4 looks different on your screen, you can’t tell if you’re doing it wrong or if everything is fine. Software updates, different device models and regional settings all change what’s on the screen, and the AI is usually describing a version that may not match yours.
Think about how a good friend would walk you through the same task over the phone. They wouldn’t just read out instructions. They’d say, “You should see a blue button now. If you see a gray one, you skipped something.” That running commentary is what a plain list leaves out.
The fix is to ask for the missing information up front.
Old way vs. new way
The old way: “How do I set up my router?” You get 10 steps. You follow them. At step 6 something looks off, and you have no idea if you broke it at step 3 or if the screen is just different from what the AI expected. You scroll back, guess and start over. Twenty minutes later you’re back at the beginning, and you still don’t know what went wrong.
The new way: You ask for the same steps, but you also ask for three extra things: what to have ready, what success looks like at each step, and the most common way each step goes wrong. Now the list is a series of checkpoints. If your screen doesn’t match, you know right away, and you know which step to fix. Instead of restarting from scratch, you back up one step and repair that one spot.
The answer gets longer. But you only read the “what to do if it goes wrong” part when you actually need it. On a good day, you skim right past it and finish faster than you would have with the plain list.
The paragraph
Here’s the prompt, straight from the original post:
Before the steps, list everything I need to have ready. For each step, tell me what I should see when it worked, and the most common way it goes wrong at that point and what to do if it does. Assume I’ve never done this before, and don’t skip steps that seem obvious.
Paste it under any how-to question. It works for tech tasks, but also for things like assembling furniture, setting up a new phone, filing an online form or following a recipe with an unfamiliar technique. Anywhere a wrong turn is hard to notice, this helps.
Why each part matters
- 🧰 “Everything I need to have ready.” A lot of stuck moments are a password, a cable or a file you didn’t know you needed until step 6. Get the shopping list first, and you won’t be digging through a drawer with a half-finished setup on your screen.
- 👀 “What I should see when it worked.” This is the big one. It turns the list into checkpoints, so you catch a wrong turn immediately instead of three steps later. A line like “the status light should turn solid green” is far more useful than “connect the device.”
- ⚠️ “The most common way it goes wrong.” The model already knows the usual failure points. It just doesn’t mention them unless you ask. Typical examples are a typo in a network name, a setting that needs a restart or a formula range that’s off by one row.
- 🪜 “Don’t skip steps that seem obvious.” The skipped “obvious” step is usually where beginners get lost. Things like “open the settings menu” or “save before closing” feel too small to mention, yet they’re often the exact thing that breaks the whole process.
How to use it
- Write your normal question, like “How do I set up a pivot table in Google Sheets?”
- Paste the paragraph right below it.
- Read the “things to have ready” section first and gather what it lists. Check it off before you touch anything else.
- Work through the steps one at a time. After each one, compare your screen to the “what you should see” line.
- Only open the “if it goes wrong” part when something doesn’t match.
- If the fix doesn’t work, reply with exactly what you see on your screen and ask the AI to adjust. You now have a precise starting point, so the conversation stays short.
This works in ChatGPT, Claude, Gemini, Grok or any other chat model, because you’re just asking for more complete instructions.
Don’t retype it every time
The only way this fails is if you forget to use it. The original poster keeps the paragraph saved in AI Toolbox, a browser extension they build, so typing // drops it under any how-to question. A plain notes file works too, as long as you actually paste it. Pick whichever you’ll really use, and put it somewhere you can reach in two clicks. If it takes longer than that, you’ll skip it on the day you need it most.
Try it on the next how-to question you have. Then come back and tell me which step it caught that a plain list would have missed!
ChatGPT’s step-by-step instructions skip exactly the step you’re going to get stuck on
by u/Ok_Negotiation_2587 in ChatGPTPromptGenius