The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+My engineering team is getting flooded with alerts from the staging pipeline. Turn off…
Execute — do the immediate task
+My engineering team is getting flooded with alerts from the staging pipeline. Turn off notifications for the staging channel for everyone except on-call engineers, then confirm that paging still works for the incident rota. Do this before the end-of-day standup on Friday and tell me what changed so I can announce it.
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 change the notifications, make the channel less noisy so engineers actually read the…
Improve — make it easier to accept
+Before I change the notifications, make the channel less noisy so engineers actually read the important ones: surface which alert types are paging, show the count of noise vs paging in the last 48 hours, suggest a short notification policy I can paste to the team that highlights only failures and deploys, and flag any alerts that will stop paging if we mute the channel.
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 muted the staging channel for myself and five engineers to reduce noise while we sprint, but I’m…
Decide — diagnose the stuck moment
+I just muted the staging channel for myself and half the team and now I worry I missed a page.
I muted the staging channel for myself and five engineers to reduce noise while we sprint, but I’m not sure if that also silenced the on-call paging. The rotation is managed by Priya and the ops rota is a separate integration. I’m afraid an incident could go unnoticed tonight. Can you tell me how likely it is I disabled pages too and the fastest way to verify and restore paging for the on-call person only?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across the last three sprints we mute noisy channels to get focus, and each time we scramble to…
Become — change the pattern
+We repeatedly mute noisy channels and then scramble when incidents happen.
Across the last three sprints we mute noisy channels to get focus, and each time we scramble to re-enable on-call pages or explain missed alerts to stakeholders. I lose credibility as the channel owner and we waste time restoring settings. Which habits around notification ownership and a lightweight policy would prevent bleed between quieting a channel and breaking paging? Suggest steps to apply before the next sprint.
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.