The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Revert the document 'Team Notes 2026-07-15' to the version saved at 3:12 p.m. today, confirm that…
Execute — do the immediate task
+Revert the document 'Team Notes 2026-07-15' to the version saved at 3:12 p.m. today, confirm that the three bullets added after that time are removed, then reproduce the restored file to the shared folder and notify Akiko that the roll-back is complete.
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 commit to a rollback, show me a concise timeline of recent edits with who made them and…
Improve — make it easier to accept
+Before I commit to a rollback, show me a concise timeline of recent edits with who made them and let me preview the version from 3:12 p.m. so I can confirm content differences; flag any comments or resolved threads that will be lost by reverting.
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 Undo repeatedly during a joint editing session and now suspect I removed Sarah's new section.…
Decide — diagnose the stuck moment
+I undid a change and now I'm not sure what was lost
I hit Undo repeatedly during a joint editing session and now suspect I removed Sarah's new section. Sarah will be upset if her work disappears. I don't know whether the content is gone permanently or sits in version history. What's the fastest way to see what changed in the last 30 minutes and recover only her section if needed?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+On tight-authoring sprints we often over-undo, losing others' contributions or comments and then…
Become — change the pattern
+Frequent accidental undos cost recovery time
On tight-authoring sprints we often over-undo, losing others' contributions or comments and then spending time restoring them from history. This creates friction with collaborators. Which change will reduce these incidents: discipline to use version snapshots, assigning one editor during sprints, or a different undo habit? Recommend one concrete practice and how to enforce it across the team.
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 word processor work people do in Google Docs.
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.