The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Record my routine for preparing the weekly forecast update: copy last week’s sheet to a new tab,…
Execute — do the immediate task
+Record my routine for preparing the weekly forecast update: copy last week’s sheet to a new tab, clear the Week column values, paste the updated sales CSV into the Input range, run the recalculation, and format the new tab with the report header. Save the recording so I can inspect and bind it to a button labeled Update Forecast.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I hand the recorded macro to the planner group, tidy it so a reviewer can follow: replace…
Improve — make it easier to accept
+Before I hand the recorded macro to the planner group, tidy it so a reviewer can follow: replace any Select and Activate sequences with direct range references, add a short header comment describing what the recording does, and ensure the recording stops if the expected Input range is missing so it fails with a clear message rather than corrupting a sheet.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I hit Record and it captured my mouse fumbling — selecting the whole sheet and hitting undo. The…
Decide — diagnose the stuck moment
+Recording picked up wrong selections
I hit Record and it captured my mouse fumbling — selecting the whole sheet and hitting undo. The resulting macro blows away formatting when run. I don’t know which parts of the code are the harmful ones and I’m nervous to hand this to the team. What’s the quickest way to clean recorded VBA so it only does the intended steps?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Analysts each record their own cleanup macros and we now have ten variants that break in different…
Become — change the pattern
+Every analyst records their own ad-hoc macros
Analysts each record their own cleanup macros and we now have ten variants that break in different ways. It costs hours to merge or fix them. What practical rules and a simple review flow will stop low-quality recordings from proliferating and keep the work repeatable?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other spreadsheet work people do in Microsoft Excel.
Recommend methods to protect the environmentRecommend ways to control or reduce riskReconcile account balancesRecord and manage field observationsRecord operational or production dataRecord shipment costs and weightsRecord survey measurementsRecord test procedures and resultsRecruit, interview, and select employeesRefresh external data connections
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.