The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Close milestone Release-1.4 now that the last PR merged and all issues are resolved. Add a final…
Execute — do the immediate task
+Close milestone Release-1.4 now that the last PR merged and all issues are resolved. Add a final comment linking the release notes and list the closed issues, then mark the milestone as completed so the release manager can publish.
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 close the milestone, make it easy to accept: surface any open issues with blockers, put…
Improve — make it easier to accept
+Before I close the milestone, make it easy to accept: surface any open issues with blockers, put the release notes summary at top, show the merged PRs that matter to customers, and flag anything that should keep the milestone open for a hotfix window.
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
+The Release-1.4 milestone has all PRs merged but issue 4798 is labeled wontfix by maintainers even…
Decide — diagnose the stuck moment
+The milestone appears ready but one issue is borderline.
The Release-1.4 milestone has all PRs merged but issue 4798 is labeled wontfix by maintainers even though QA flagged it. I am worried closing the milestone will hide the customer-visible regression. Should I close it now and move that issue to the next milestone, or keep this milestone open until we resolve QA’s concern? What’s the likely impact either way?
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 several releases I closed milestones as soon as merges finished, then had to reopen for…
Become — change the pattern
+I keep closing milestones that later need hotfixes.
Over several releases I closed milestones as soon as merges finished, then had to reopen for hotfixes and emergency patches. That creates churn for release notes and confuses customers. What habit change or gate should I add before closing milestones to reduce post-release hotfixes?
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.