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 the commit tagged before release. Tag commit 8f3b2a4 with v1.4.0, add the release note: "Fix…
Execute — do the immediate task
+I need the commit tagged before release. Tag commit 8f3b2a4 with v1.4.0, add the release note: "Fix memory leak in cache and bump timeout to 30s", sign the tag, and push to origin. Do a quick check that CHANGELOG.md references v1.4.0 before you push.
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 tag 8f3b2a4 for release, make the tag reviewable: surface any code changes touching…
Improve — make it easier to accept
+Before I tag 8f3b2a4 for release, make the tag reviewable: surface any code changes touching cache/timeout, list related open issues and PRs, and flag anything that would make a reviewer hesitate to accept v1.4.0 (breaking changes, migrations, or missing tests). Show the exact files and lines changed for the cache fix.
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
+We fixed a memory leak in cache on commit 8f3b2a4 but some customers run the older cache layout;…
Decide — diagnose the stuck moment
+I just realized the bugfix might break older deployments
We fixed a memory leak in cache on commit 8f3b2a4 but some customers run the older cache layout; I’m unsure if tagging v1.4.0 will force a migration they can’t handle. Who else on the team should I ask about backward compatibility, what exact compatibility checks should I run on this commit, and what’s the safest next move if I can’t confirm compatibility before Friday?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over the last six releases we’ve repeatedly pushed tags that needed immediate patches. Where are we…
Become — change the pattern
+We keep rushing tags that require hotfixes later
Over the last six releases we’ve repeatedly pushed tags that needed immediate patches. Where are we losing control — in code review, test coverage, or release gating — and what three practical habits should we adopt to stop shipping tags that force emergency fixes? Start with a single checklist item I can enforce today.
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.