The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Create a channel reminder for #backend for Wednesday at 9:00 AM to post the deployment checklist…
Execute — do the immediate task
+Create a channel reminder for #backend for Wednesday at 9:00 AM to post the deployment checklist and request approvals from on-call engineers. Set it to repeat weekly until the release is marked done.
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 post the recurring channel reminder in #backend, make the message reviewer-friendly: put…
Improve — make it easier to accept
+Before I post the recurring channel reminder in #backend, make the message reviewer-friendly: put the four checklist items up top, attach the deployment runbook link, call out who must approve (on-call: Ravi, Sasha), and highlight the escape window timing. Mark any items that typically block approval.
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 set a weekly reminder in #backend for the deployment checklist. Ravi and Sasha often don't…
Decide — diagnose the stuck moment
+I scheduled channel deployment reminders but approvals still lag
I set a weekly reminder in #backend for the deployment checklist. Ravi and Sasha often don't respond quickly and the release slips. I am worried the reminder is being ignored or lost among other messages. I cannot change their workload. What changes to the reminder content or timing are most likely to get on-call engineers to act reliably?
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 keep adding weekly reminders in #backend and approval response rates stay low, causing repeated…
Become — change the pattern
+Recurring channel reminders don't change reviewer behaviour
We keep adding weekly reminders in #backend and approval response rates stay low, causing repeated release delays. Where am I wasting time with reminders, and what different habit or escalation should I adopt to actually get timely approvals across releases?
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.