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'm about to run the demo in the weekly stakeholder call. Share your screen in the #weekly-demo…
Execute — do the immediate task
+I'm about to run the demo in the weekly stakeholder call. Share your screen in the #weekly-demo meeting five minutes early, open the prototype build at http://staging.example.com and the bug board filtered to this sprint, then present the feature flow from login to checkout. If the presenter handoff to Raj is needed, stop on slide three and give him control.
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 share my screen in the stakeholder meeting, make the view reviewer-friendly: close…
Improve — make it easier to accept
+Before I share my screen in the stakeholder meeting, make the view reviewer-friendly: close unrelated tabs, enlarge the section with the new metrics, switch the bug board to list view and highlight the three high-priority issues, and prep a one-line explanation of any latency the reviewer will see. Flag anything that would make a reviewer hesitate to approve the demo.
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 began screen sharing and mid-demo someone noticed a private chat and asked if I was exposing…
Decide — diagnose the stuck moment
+I started sharing but someone called out a private window
I began screen sharing and mid-demo someone noticed a private chat and asked if I was exposing other work. I froze and stopped explaining. I’m worried I exposed confidential info and made the team look unprepared. Do I keep going, apologize and continue, or stop and restart with a clean view? Advise the next move and exact words to say to calm the room.
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 lose time and trust because presenters habitually share cluttered screens or the wrong window. I…
Become — change the pattern
+Too many demos start with messy screens and distractions
We lose time and trust because presenters habitually share cluttered screens or the wrong window. I think it’s sloppy rehearsal and poor controls. Which routine should I institute—what checklist to run five minutes before share, who enforces it, and a quick recovery script if something slips through?
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.