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 the architecture diagram our ops lead uploaded last month so I can attach it to the outage…
Execute — do the immediate task
+I need the architecture diagram our ops lead uploaded last month so I can attach it to the outage RCA. Search the channel history for messages from Miguel in #infra between June 3 and June 18 that mention 'architecture diagram' or 'network diagram', find the latest PNG or PDF, download it, and confirm the filename and timestamp before I attach it to the RCA.
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 send this to the executive review, make the file easy to find — surface the most recent…
Improve — make it easier to accept
+Before I send this to the executive review, make the file easy to find — surface the most recent diagram at the top, show who uploaded it and when, highlight whether it’s PNG or PDF, and flag any similarly named files that might be older versions so a reviewer won't grab the wrong one.
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 searched for Miguel's architecture diagram and pulled dozens of results across #infra, #ops, and…
Decide — diagnose the stuck moment
+I tried the search query and got dozens of matches from different channels.
I searched for Miguel's architecture diagram and pulled dozens of results across #infra, #ops, and DMs. I need the single most recent authoritative diagram for the June outage RCA. Tell me the best steps to narrow to the correct file quickly, what specific search terms and date range to run, and how to confirm it’s the canonical version.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over the last year we spend time grabbing outdated network diagrams and re-running RCAs. Where are…
Become — change the pattern
+We keep re-finding old diagrams and attaching wrong versions.
Over the last year we spend time grabbing outdated network diagrams and re-running RCAs. Where are we losing time and credibility — naming conventions, upload discipline, or channel chaos? Recommend one habit change and a lightweight rule to stop people from attaching stale diagrams to reports.
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.