The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+This channel is for the backend engineering team to coordinate daily deployments, incident triage,…
Execute — do the immediate task
+This channel is for the backend engineering team to coordinate daily deployments, incident triage, and on-call handoffs. Pin the deployment checklist and current on-call roster, and set the topic to include the primary support window (08:00–20:00) and pager escalation path. Confirm the topic displays on mobile and desktop before leaving.
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 set the channel purpose for backend deployment work, make the critical signals obvious:…
Improve — make it easier to accept
+Before I set the channel purpose for backend deployment work, make the critical signals obvious: put the deployment window and phone-tree at the top, link to the rollback playbook, and flag ‘do not merge’ hours. Call out what would make reviewers hesitate: ambiguous on-call names, missing playbook link, or unclear escalation. Keep the purpose under two lines for quick scanning.
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 made a channel for backend deployments and wrote a long, polite purpose that mentions deploys,…
Decide — diagnose the stuck moment
+We just created a new channel for backend deploys
I made a channel for backend deployments and wrote a long, polite purpose that mentions deploys, incidents, and on-call. I’m worried people will ignore it or the wrong person will be paged. I can’t tell if the on-call roster is official. What’s the likely problem and the best next move to make this purpose reliable and used?
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 projects we spend time drafting detailed channel purposes that no one reads; later we get…
Become — change the pattern
+Channel purposes get wordy and ignored
Across projects we spend time drafting detailed channel purposes that no one reads; later we get paged and blame the topic. Which simple habit will stop wasted drafting and make topics actually guide behavior?
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.