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 start a focused thread under Marcus's design note so discussion stays organized. Begin a…
Execute — do the immediate task
+I need to start a focused thread under Marcus's design note so discussion stays organized. Begin a threaded reply under his message in #product with: a brief agreement, one open question about edge cases, and a proposal for a 15-minute sync tomorrow at 11am PT.
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 start the thread, make the reply easy for engineers to act on: surface the decision needed…
Improve — make it easier to accept
+Before I start the thread, make the reply easy for engineers to act on: surface the decision needed in the first sentence, list two specific technical concerns that could block implementation, and end with a clear suggested time for a short meeting. Keep it skimmable.
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
+Marcus shared a UI flow and asked for feedback. I worry about load on the backend and missing…
Decide — diagnose the stuck moment
+Marcus posted a design and I don't know if we should accept it or ask for more detail
Marcus shared a UI flow and asked for feedback. I worry about load on the backend and missing analytics events but I don't want to derail progress. I can't tell if leadership expects quick approval or a deeper review. What's the likely expectation and the best one-paragraph thread starter to prod useful responses?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+I keep opening new threads for small clarifications and teammates stop replying. Over the last two…
Become — change the pattern
+I start threads for every minor point and drown people
I keep opening new threads for small clarifications and teammates stop replying. Over the last two weeks that has delayed decisions. Which habit about when to thread (vs. DM or inline) should I adopt, and how do I enforce it so discussions stay timely?
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.