The moments that lead here
If one of these is your afternoon, you are in the right place.
across the last 12 procedures, techs still ask the same three questions on day one
1 ready prompt
Written for the moment this actually comes up.
Become — change the pattern
+Across the last [N=12] install procedures I’ve produced, techs repeatedly ask the same three…
Become — change the pattern
+Across the last [N=12] install procedures I’ve produced, techs repeatedly ask the same three clarifying questions during first installs. Show the pattern where our writing fails—are we missing steps, images, or signoffs? Recommend one durable habit I should adopt that reduces those starter questions: a checklist, a required field test, or a standard engineering signoff. Explain the trade-off in time for adoption versus fewer support calls.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Who does this, and with what
The same task is different work inside a different job.
Technical WriterAdobe Acrobat
Next to this one
Other record work people do in Adobe Acrobat.
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.