The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Add Jessica Rivera and Omar Khan to the backend-deployments channel, remove inactive contractors…
Execute — do the immediate task
+Add Jessica Rivera and Omar Khan to the backend-deployments channel, remove inactive contractors Tom Lee and Priya Patel, and confirm that all members have the correct display names and team tags. After updating, post a short welcome that explains why Tom and Priya were removed and who to contact to be re-added.
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 adjust channel membership for backend-deployments, surface the things that make approval…
Improve — make it easier to accept
+Before I adjust channel membership for backend-deployments, surface the things that make approval easy: show who is active in rotation, list contractors whose access expires, and highlight any skipped compliance training. Call out hesitation drivers: removing someone still on pager duty, losing historical context when someone is removed, or breaking cross-team visibility. Suggest a simple audit and message to explain changes.
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 cleaned up the channel by removing people listed inactive last month. A PM messaged asking why…
Decide — diagnose the stuck moment
+I removed inactive members and now someone asked why
I cleaned up the channel by removing people listed inactive last month. A PM messaged asking why they lost access; they say they still need to see deploy notes. I don’t know their exact role or approval path to re-add them. What likely mistake did I make and what’s the fastest defensible next step so visibility is restored without expanding access unnecessarily?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over time we spend hours fixing channel membership after heads-down work—people get added for a…
Become — change the pattern
+We keep adding and removing people ad hoc and lose track
Over time we spend hours fixing channel membership after heads-down work—people get added for a sprint, then forgotten, then removed, causing access gaps. What single recurring habit and an easy weekly check can reduce churn and prevent accidental lockouts?
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.