The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Watch the repository infra-team/ansible-roles so I get notifications on issues and PRs during the…
Execute — do the immediate task
+Watch the repository infra-team/ansible-roles so I get notifications on issues and PRs during the rollout next Tuesday. Use my account marco.ops and set notifications to watch for all activity. Confirm the change and the notification level.
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 set watch on infra-team/ansible-roles, make the watch useful: suggest a notification level…
Improve — make it easier to accept
+Before I set watch on infra-team/ansible-roles, make the watch useful: suggest a notification level (all activity, releases only, or participating) based on my role as release lead, show recent notification volume so I can avoid alert fatigue, and warn if multiple team members already watch it. Recommend the setting that balances awareness and noise for the rollout next Tuesday.
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 flipped watch on infra-team/ansible-roles to follow a deploy and immediately started getting…
Decide — diagnose the stuck moment
+I toggled watch and notifications exploded
I flipped watch on infra-team/ansible-roles to follow a deploy and immediately started getting dozens of notifications. I’m unsure whether I chose the wrong notification level or if the project has unusually high churn. What’s the fastest way to reduce noise now, retain visibility on critical PRs, and set a sustainable notification level for the team during the rollout?
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 incident the whole ops crew watches several repos and then suffers notification fatigue for…
Become — change the pattern
+we react to outages with everyone watching repos indiscriminately
Every incident the whole ops crew watches several repos and then suffers notification fatigue for weeks. How should we change our incident monitoring and watching practices so only the right people get alerts and we stop losing focus after every outage?
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 code hosting work people do in GitHub.
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.