The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Promote Aaron Mills to channel admin in the ops-coordination channel so he can manage pins and…
Execute — do the immediate task
+Promote Aaron Mills to channel admin in the ops-coordination channel so he can manage pins and invites. Verify he has the correct role in LDAP, tell him he must announce admin changes, and schedule a 15-minute handover with current admins on Friday to review pinned items and automations.
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 Aaron an admin, surface the reviewer’s concerns: which admin privileges he needs,…
Improve — make it easier to accept
+Before I make Aaron an admin, surface the reviewer’s concerns: which admin privileges he needs, whether he has training on approvals and removals, and which automations will be affected. Flag hesitation points: giving admin rights to someone off-rotation, missing two-person approval for member removal, or breaking the audit trail. Recommend a brief handover checklist and a 24-hour observation period.
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 granted admin rights to Aaron so he could manage invites; afterwards several pinned messages and…
Decide — diagnose the stuck moment
+I promoted someone to admin and now pins disappeared
I granted admin rights to Aaron so he could manage invites; afterwards several pinned messages and an integration behaved differently. I’m not sure if I missed a permission toggle or an app mapping. What likely happened and what’s the quickest way to confirm admin privileges without upsetting Aaron?
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 repeatedly make people channel admins for a task and forget to revoke rights; later a…
Become — change the pattern
+We hand out admin rights casually and later regret it
We repeatedly make people channel admins for a task and forget to revoke rights; later a misconfigured bot or accidental removals cause outages. What policy or lightweight habit would stop admin creep while keeping operations agile?
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.