The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I must answer Priya's question in the deployment thread with a clear next step. Reply in the thread…
Execute — do the immediate task
+I must answer Priya's question in the deployment thread with a clear next step. Reply in the thread saying we will roll back to the previous release now, list the rollback steps I will run, and promise an incident postmortem by Friday at 4pm.
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 posting the thread reply, make it easy for the incident commander to act: surface the chosen…
Improve — make it easier to accept
+Before posting the thread reply, make it easy for the incident commander to act: surface the chosen action first, add three concise rollback commands in code-style lines, and call out the single risk that could block rollback. Keep it under five lines.
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
+We lost traffic after the last deploy and the commander asked whether to pause. I'm unsure if the…
Decide — diagnose the stuck moment
+The incident commander asked if we should pause the rollout and I hesitate
We lost traffic after the last deploy and the commander asked whether to pause. I'm unsure if the metric drop is noise or a real regression and I cannot see the full logs. I fear suggesting rollback if it's noise or delaying if it's real. What's the likely correct call and the one-line reply I should post in the thread?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+I habitually write long thread replies during incidents and engineers skim past them, missing…
Become — change the pattern
+My thread replies are long and people ignore them
I habitually write long thread replies during incidents and engineers skim past them, missing actions. Which three habits will make my thread replies more actionable and how do I practice them in the next two incidents?
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.