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 need everyone on the product and infra squads together for an urgent sync. Start a video call in…
Execute — do the immediate task
+I need everyone on the product and infra squads together for an urgent sync. Start a video call in the #release-room channel now and invite Maria, Jae, Luis, and the on-call engineer, in that order. Wait until Maria confirms she can join, then start. If more than one person declines, pause and ping me before proceeding.
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 call the cross-team group, make joining frictionless: put the agenda and two attachments…
Improve — make it easier to accept
+Before I call the cross-team group, make joining frictionless: put the agenda and two attachments (deploy plan, rollback checklist) in the channel thread, list the main decision and the single ask for each attendee, and add a note that the call will start on time even if a few are late. Highlight the one point likely to trigger pushback.
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 up an emergency video call for the release and pinged the usual list. Two engineers replied…
Decide — diagnose the stuck moment
+I scheduled an urgent call; two engineers say they can't join
I set up an emergency video call for the release and pinged the usual list. Two engineers replied they are deep in a blocker and can’t join. I’m worried decisions will be made without their input and that I haven’t explained the consequences clearly. Should I postpone until they can join, pull a quick deputy to represent them, or continue and document decisions afterward? Recommend the likeliest safe choice and the exact message to send.
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 starting syncs without the engineers who actually own the risk, then scramble to undo…
Become — change the pattern
+Repeatedly starting calls with missing critical people
We keep starting syncs without the engineers who actually own the risk, then scramble to undo decisions. Where am I losing credibility and time? I think I book on short notice and assume others will reprioritize. What habit should I change to stop this—how to change invites, preflight checks, and my escalation so their presence is reliable?
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.