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 to share the latest heap dump and a screenshot of the profiler with SREs. Post the two files…
Execute — do the immediate task
+I need to share the latest heap dump and a screenshot of the profiler with SREs. Post the two files into #sre-debug with this note: Attached: heapdump-2026-07-17.hprof and profiler-2026-07-17.png. Repro steps are in the first file. Please start with heapdump analysis; @Lina and @Diego, can you pick this up?
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 drop the heap dump and profiler screenshot into #sre-debug, surface the quick triage cues…
Improve — make it easier to accept
+Before I drop the heap dump and profiler screenshot into #sre-debug, surface the quick triage cues so they know what to look for first: name the suspected service, attach the repro steps, estimate the time to get initial findings, and flag confidentiality. Message: Service: payments-api. Files: heapdump-2026-07-17.hprof, profiler-2026-07-17.png. Repro: steps 1–4 in heapdump file. Expected first-pass: 30–45m. Private to SREs. Please assign: @Lina first, @Diego backup.
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 just uploaded heapdump-2026-07-17.hprof and profiler-2026-07-17.png but I’m worried the SREs will…
Decide — diagnose the stuck moment
+I captured a heap dump and a profiler screenshot but I don’t know how to make the handoff clear.
I just uploaded heapdump-2026-07-17.hprof and profiler-2026-07-17.png but I’m worried the SREs will miss the repro steps or not prioritize it. I don’t know who’s on-call for payments-api tonight. Who should I call out, what minimal guidance do I need to give so they can start triage immediately, and how do I protect the files from being shared outside SRE?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every incident I throw heap dumps and screenshots into channels without a clear owner; I end up…
Become — change the pattern
+I keep dumping large debug files into channels and then chasing people to look at them.
Every incident I throw heap dumps and screenshots into channels without a clear owner; I end up pinging people repeatedly and waiting hours for a reply. Where is the real time loss and what routine should I adopt so each handoff includes owner, ETA, and sensitivity level and reduces follow-ups?
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.