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 remember to follow up on the build validation results. Create a personal reminder for…
Execute — do the immediate task
+I need to remember to follow up on the build validation results. Create a personal reminder for Friday at 3:00 PM to review the test logs and publish any critical failures to the incident channel. Remind me 30 minutes before.
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 save this reminder to myself, make it actionable: include the team folder path to the test…
Improve — make it easier to accept
+Before I save this reminder to myself, make it actionable: include the team folder path to the test logs, list the exact log names to check (unit-tests.log, integration.log), and note the threshold that counts as critical (more than 5 failures in integration.log). Flag if any previous follow-up is still open.
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 said I would triage the build failures and I created a vague mental note. Priya and Marco expect…
Decide — diagnose the stuck moment
+I just promised triage in standup and set no follow-up
I said I would triage the build failures and I created a vague mental note. Priya and Marco expect an update tomorrow. I am worried I will miss logging the critical ones and lose credibility. I cannot tell them I already forgot details. What is the quickest, defensible next step to capture the follow-up and keep their trust?
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 sprint I tell the team I will check failing builds, then I rely on memory and miss a few,…
Become — change the pattern
+I rely on ad-hoc personal reminders and then miss follow-ups
Every sprint I tell the team I will check failing builds, then I rely on memory and miss a few, which costs credibility and creates fire drills. Which small habit will stop this pattern—something I can do in under two minutes after each standup—and how do I make the team hold me accountable for the first three sprints?
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.