The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+We’re getting too many interruptions from #dev-discuss during the release window. Mute that channel…
Execute — do the immediate task
+We’re getting too many interruptions from #dev-discuss during the release window. Mute that channel for the next six hours so the release lead and oncall can focus unless someone mentions @release or my name.
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 mute #dev-discuss, surface what I’ll miss: show pinned alerts, any scheduled standup…
Improve — make it easier to accept
+Before I mute #dev-discuss, surface what I’ll miss: show pinned alerts, any scheduled standup reminders, and whether someone has recently @here’d or @channel’d. Flag words that should bypass mute like security or outage so I don’t silence critical alarms by accident.
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
+During the last release, #dev-discuss kept pinging the team and we lost focus. If I mute the…
Decide — diagnose the stuck moment
+The release got derailed by constant chatter from a noisy channel
During the last release, #dev-discuss kept pinging the team and we lost focus. If I mute the channel for six hours, will mentions of @release still come through? If not, what’s the safest mute configuration so the team isn’t disrupted but legitimate release mentions still alert us?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Our team repeatedly gets derailed during releases and oncall shifts by noisy channels. What routine…
Become — change the pattern
+We repeatedly get derailed by noisy channels at critical moments
Our team repeatedly gets derailed during releases and oncall shifts by noisy channels. What routine should we adopt to manage channel muting: who decides when to mute, which keywords or mentions must bypass mute, and how do we communicate the mute to avoid missed emergencies? Give a short checklist the release lead can follow.
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.