The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Enable the integrations for the support operations board that the team requested. Turn on Slack…
Execute — do the immediate task
+Enable the integrations for the support operations board that the team requested. Turn on Slack notifications to the support-ops channel for new high-priority cards, enable the time-tracking integration for all cards in the In Progress list, and connect the repo so linked commits appear on cards. Test each integration and report any permission prompts that need admin approval.
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 enable these integrations for the whole support group, make the setup easy to approve —…
Improve — make it easier to accept
+Before I enable these integrations for the whole support group, make the setup easy to approve — surface which integrations push notifications externally, call out who will receive each alert and how often, and flag any changes that could increase noise for on-call engineers. Recommend sensible defaults to avoid alert fatigue.
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 turned on Slack notifications and the support-ops channel was flooded with card updates; the…
Decide — diagnose the stuck moment
+I enabled integrations and Slack exploded with alerts.
I turned on Slack notifications and the support-ops channel was flooded with card updates; the on-call engineers are annoyed and I don’t know which integration or rule caused it. What is the most likely source of the noise and which immediate change will quiet alerts without hiding critical incidents?
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 losing credibility because integrations either flood teams with alerts or require multiple…
Become — change the pattern
+Every time I enable integrations they create noise or permission problems.
I keep losing credibility because integrations either flood teams with alerts or require multiple admin approvals I didn’t anticipate. What configuration habit or approval checklist should I adopt so integrations behave predictably and stakeholder pushback drops sharply?
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 kanban boards work people do in Trello.
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.