Fresh drop from r/PromptEngineering: the creator of Midum, a free, source-available AI runtime, just rolled out an experimental feature called step-prompting. Instead of hoping the model follows your bullet list, you give it a checklist it’s actually held to. Anyone who has pasted a seven-point instruction block into a chat and watched the model quietly skip points four and six will see why this is worth a look.
The twist is that this is not just bullet points in a prompt. You define the steps in a panel that sits over the prompt box. When you send, the model gets those steps again on every response and every tool turn, along with instructions to follow them. It checks them off one by one. Per the creator, that gives the model a strict, system-governed incentive to finish the list, which plain text in a prompt doesn’t.
Think about why that matters. With a normal prompt, your instructions appear once at the top. By the time the model has made a few tool calls, read a few files, or written a long answer, those instructions are buried under a pile of newer context. Step-prompting keeps resurfacing the checklist, so the model keeps seeing what is done and what is still open. It’s the difference between a sticky note you wrote this morning and a task board that stays open on the screen next to you.
Two more things make it interesting. You can ask the model to provide proof for each step, so it has to show it did the thing. And if you don’t write any steps, the model can write its own when it decides a checklist would help.
Proof is the part I like most. Say step three is “run the tests and fix any failures.” Without verification, the model can say “done” and move on. With verification on, it has to show something real, like the test output or the diff it made. For work where a silent skip is expensive, such as refactors, data cleanup, or research tasks with a required source for every claim, that one setting could save you a lot of rereading.
The self-written steps are a nice fallback too. If you throw a messy, open-ended request at the model, it can break the job into a list on its own and then hold itself to that list. You get structure even when you didn’t have time to plan one.
The creator says completion rates in their testing were significantly higher than with the same steps as bullets. That’s their own testing, so treat it as a promising claim and not a benchmark. The post has just 3 upvotes and no comments yet, so nobody has independently checked it. Early and unverified is fine for a free experimental feature, as long as you go in knowing that. The idea is plausible, but plausible is not proven.
Here’s the mini-workflow:
- 🧭 Open the steps panel above the prompt box and write your steps in order. Keep each step small and checkable. “Update the README” is vague. “Add an install section to the README with the exact command” is a step the model can actually finish and prove.
- ✅ Toggle verification if you want the model to prove each step is done. Good for anything where “I did it” isn’t enough on its own.
- 🔢 Optionally cap how many steps the model does in one response. This keeps each reply short enough to review.
- 🚀 Send the prompt. The steps ride along on every turn until they’re checked off. Watch the list as it fills in, and if the model gets stuck on one step, you will see it right away instead of discovering it at the end.
Pro tips
- If you want to compare step-prompting against plain bullets, turn off the tool that lets the model write its own steps first. Otherwise it converts your bullets into steps itself and the test is meaningless. The creator flags this directly. For a fair test, run the exact same task twice with the same wording, once as bullets and once in the panel, and count how many steps each run finished.
- Use the step cap for long jobs. Doing a few steps per response is easier to review than one giant dump. A twelve-step migration is much easier to trust when you approve it in chunks of three or four.
- Use verification on the steps you care most about. Asking for proof on everything will slow things down. Save it for the steps where a quiet failure would hurt, like deleting files, changing configs, or anything that touches real data.
- Order your steps so that later ones depend on earlier ones. When the checklist keeps coming back on every turn, a clear sequence helps the model see what to do next.
The app is free on GitHub and the Microsoft Store. The creator is asking this community for feedback, so if you run a side-by-side test, tell them what you see. I’d love to hear your results too ⚓ Drop them in the comments!
Rolled out a new experimental step-prompting feature in my free AI app
by u/ConsistentFox567 in PromptEngineering