The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Integrate the monitoring tool with #alerts so Pager duty notifications and CPU spike alerts post…
Execute — do the immediate task
+Integrate the monitoring tool with #alerts so Pager duty notifications and CPU spike alerts post there. Configure notifications to notify @oncall and to post error summaries, not raw traces. Test once and report success to the SRE lead.
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 connect the monitoring app to #alerts, make the integration respectful of channel noise:…
Improve — make it easier to accept
+Before I connect the monitoring app to #alerts, make the integration respectful of channel noise: group similar alerts into one summary message, include severity tags, send only actionable links, and suppress known maintenance windows. Highlight who will own the initial triage and what the channel should not be used for.
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 just hooked the monitoring feed into #alerts and the channel filled with noisy, low-priority…
Decide — diagnose the stuck moment
+I turned on an integration and #alerts went noisy
I just hooked the monitoring feed into #alerts and the channel filled with noisy, low-priority messages. The team is annoyed and the on-call rota is complaining. I can't unring the bell. What immediate configuration changes will calm the channel while preserving critical alerts, and how do I communicate the fix to the team so they know I'm on it?
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 add integrations to #alerts and the channel becomes noisy, causing us to miss real…
Become — change the pattern
+Integrations keep flooding channels with low-value noise
We repeatedly add integrations to #alerts and the channel becomes noisy, causing us to miss real incidents and wasting engineer attention. Where are we going wrong when deciding what to connect and how, and what clear rule should I adopt for future integrations to protect signal without losing important alerts?
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.