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 find every mention of 'database migration' across the workspace from the last six months,…
Execute — do the immediate task
+I need to find every mention of 'database migration' across the workspace from the last six months, including private channel posts where I am permitted, and assemble them in chronological order into a single document for the release review. Also pull the last three messages from each thread and surface any action items or decisions.
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 run a workspace-wide search for 'database migration', make results reviewer-friendly. Put…
Improve — make it easier to accept
+Before I run a workspace-wide search for 'database migration', make results reviewer-friendly. Put the earliest mention and any decision summaries at the top, group hits by channel and date, surface repeated action items, and highlight messages that include a clear owner or deadline so reviewers can scan quickly.
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 ran a search for 'database migration' and got hundreds of hits across channels and DMs; I'm…
Decide — diagnose the stuck moment
+Search returned hundreds of hits and I froze.
I ran a search for 'database migration' and got hundreds of hits across channels and DMs; I'm afraid I'll miss the single message that sets the production rollback plan. I don't know which channels hold final decisions versus chatter. How should I triage the results so I find authoritative signoffs and the rollback instructions fast?
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 repeatedly lose final decisions and rollback plans inside long chat threads so release reviewers…
Become — change the pattern
+We lose decision context in chat threads.
We repeatedly lose final decisions and rollback plans inside long chat threads so release reviewers waste hours hunting for confirmation. What habit, naming convention, or tiny process change would keep operational decisions discoverable in searches without policing everyone's messages?
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.