The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I need to remove Alex Mendoza's admin privileges in the engineering channel and across the…
Execute — do the immediate task
+I need to remove Alex Mendoza's admin privileges in the engineering channel and across the workspace. Demote Alex from owner to member, but before I touch anything confirm which channels, integrations, and scheduled messages rely on Alex's credentials and whether Alex is the primary owner of any apps. Do the demotion on Friday at 5pm after I review the checklist, and notify Alex and the security lead once 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 demote Alex Mendoza, make the change as painless as possible for reviewers in Security and…
Improve — make it easier to accept
+Before I demote Alex Mendoza, make the change as painless as possible for reviewers in Security and Platform. Surface a short summary at the top showing which channels will lose admin-level settings, list integrations and scheduled jobs tied to Alex, flag any places where demotion will block deployment or alerts, and suggest a fallback owner for each risk item.
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 opened the Owner settings and hesitated because Alex is listed as the primary contact for two…
Decide — diagnose the stuck moment
+I clicked Owner settings and hesitated.
I opened the Owner settings and hesitated because Alex is listed as the primary contact for two alerting integrations and a CI webhook. I do not know whether those integrations will stop posting if ownership changes, and I cannot tell if there is an alternate admin available. What is most likely to break on demotion and what is the safest immediate next step?
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 delaying demotions and owner transfers until a deployment or alert causes an outage. Each…
Become — change the pattern
+We keep delaying admin changes until an outage.
We keep delaying demotions and owner transfers until a deployment or alert causes an outage. Each time, last-minute firefights create emergency privilege escalations. How should we change our routine so admin handoffs are planned and tested, who should own the checklist, and what small habit will stop us from waiting for an incident?
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 team chat work people do in Slack.
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.