The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Post the bug report in #backend as a formatted message: include the stack trace in a code block,…
Execute — do the immediate task
+Post the bug report in #backend as a formatted message: include the stack trace in a code block, the reproduction steps as numbered items, and a short summary at the top. Tag Marcus and Claire so they get notified and ask for fixes by end of day Friday. Verify the code block preserves indentation and long lines.
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 bug in #backend, make the message easy for reviewers to act on: put the failing…
Improve — make it easier to accept
+Before I post the bug in #backend, make the message easy for reviewers to act on: put the failing assertion and exact error string right up top, collapse the long stack trace into a downloadable paste and show the reproduction steps as three clear commands. Flag anything that would make a reviewer hesitate to triage this issue.
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 posted a bug in #backend with a long, unformatted stack trace; Marcus skimmed and didn’t…
Decide — diagnose the stuck moment
+I pasted a long stack trace and people ignored the message.
I just posted a bug in #backend with a long, unformatted stack trace; Marcus skimmed and didn’t respond. I’m afraid the missing context and noisy trace buried the real error and delayed triage. What’s the concrete way to reformat and resend this so it gets immediate attention without spamming the channel?
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 regularly announce bugs in #backend with long traces and unclear next steps and engineers don’t…
Become — change the pattern
+Our posted bug reports in chat consistently fail to get traction.
We regularly announce bugs in #backend with long traces and unclear next steps and engineers don’t triage them promptly, which slows our sprint. What change to our message template, tagging rules, or channel culture would get faster responses and clearer ownership for every report?
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.