The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Pin the deployment checklist message in #platform-deployments so everyone can find it. Confirm with…
Execute — do the immediate task
+Pin the deployment checklist message in #platform-deployments so everyone can find it. Confirm with Raj that the checklist is the latest version, then pin it now and add a one-line note pointing to the linked runbook.
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 pinning the deployment checklist in #platform-deployments, make it frictionless to use.…
Improve — make it easier to accept
+Before pinning the deployment checklist in #platform-deployments, make it frictionless to use. Verify the checklist has the current rollback steps, surface the estimated execution time at the top, and add a short example of what success looks like so reviewers don’t hesitate to follow it.
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 revised the deployment checklist in #platform-deployments, but the old checklist is still pinned…
Decide — diagnose the stuck moment
+I posted an updated checklist but someone in ops may rely on the old one pinned in the channel.
I revised the deployment checklist in #platform-deployments, but the old checklist is still pinned and people might follow it. I’m afraid a pinned outdated checklist could cause a failed deploy and I don’t know who pinned it originally. Should I unpin the old one and pin this immediately, or announce the change first and risk it being missed?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+In active channels pins pile up until nobody finds the truly important documents. Our incident…
Become — change the pattern
+Pins accumulate and the channel’s pin list becomes noise instead of a quick reference.
In active channels pins pile up until nobody finds the truly important documents. Our incident channel has eight pins and responders waste minutes hunting for the runbook. What rules and a lightweight maintenance habit should we introduce so pins remain a reliable, trusted signal for the team?
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.