The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Prepare a zip of the Q2 deliverables folder and download it so I can send it to legal. Include the…
Execute — do the immediate task
+Prepare a zip of the Q2 deliverables folder and download it so I can send it to legal. Include the contracts, the final slide deck, and the invoice PDF in that order. Confirm the zip completes without file-count or filename errors and that the file size fits under a 500 MB email attachment before I upload to the portal.
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 make a zip for legal, make the download less painful to review: put the contracts in a…
Improve — make it easier to accept
+Before I make a zip for legal, make the download less painful to review: put the contracts in a Contracts subfolder, rename the slide deck to include date and version, and remove duplicate drafts. Flag any files over 100 MB and any filenames with special characters that might break extraction on Windows.
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 tried to download the Q2 deliverables as a zip and the job failed with a filename/encoding error…
Decide — diagnose the stuck moment
+The zip failed midway with a filename error.
I tried to download the Q2 deliverables as a zip and the job failed with a filename/encoding error halfway through. I’m not sure which file caused it and legal needs the package today. What’s the most likely culprit, which quick checks find the bad filename, and the fastest workaround so I can produce a usable zip in the next hour?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We keep failing archives because of inconsistent filenames, duplicates, and occasional huge raw…
Become — change the pattern
+Creating zips repeatedly trips on filenames and large files.
We keep failing archives because of inconsistent filenames, duplicates, and occasional huge raw exports. Which two habits should I change so zips succeed first try: one naming/organization rule to apply to all deliverable folders, and one pre-download check to run before creating an archive?
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 file storage work people do in Google Drive.
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.