The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Set post visibility for next week's product announcement so only subscribers see it until launch.…
Execute — do the immediate task
+Set post visibility for next week's product announcement so only subscribers see it until launch. For the product-announcement post titled 'SmartCharge 3 Launch' set visibility to Private for internal review, then schedule it to Password Protected visible to newsletter subscribers on July 20, and finally Public on July 27 at 09:00. Confirm the visibility steps in that order.
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 publish this post to the wider audience, make the visibility easy to audit. Surface the…
Improve — make it easier to accept
+Before I publish this post to the wider audience, make the visibility easy to audit. Surface the current visibility state up top, show who last changed it and when, make the publish and visibility schedule findable, and flag any posts that have inconsistent scheduled visibility versus publish times that could leak content early.
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 flicked a post to Private to hide it but a draft ended up public and a partner spotted it. I…
Decide — diagnose the stuck moment
+I changed visibility and now a draft is public
I flicked a post to Private to hide it but a draft ended up public and a partner spotted it. I don't know whether the mistake was a visibility toggle, a cached page, or a scheduled publish. What's the most likely cause, how do I immediately contain the leak, and what check will prevent it next time?
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 leaking drafts or embargoed posts, costing trust with partners and customers. Where is our…
Become — change the pattern
+We repeatedly expose drafts or embargoed posts prematurely
We keep leaking drafts or embargoed posts, costing trust with partners and customers. Where is our process failing—who touches visibility, what UI steps encourage mistakes, or are schedules handled poorly—and what one procedural change plus one pre-publish check would stop the leaks for good?
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 website builder work people do in WordPress.
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.