The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Assign issue 4821 to Marco and put Priya in the assignees as watcher; include a note that Marco…
Execute — do the immediate task
+Assign issue 4821 to Marco and put Priya in the assignees as watcher; include a note that Marco should pick this up by Wednesday and Priya will validate the fix. Verify Marco is available by checking his open PRs first to avoid conflicts.
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 assign this to someone, make it easy for the team lead to approve: surface each…
Improve — make it easier to accept
+Before I assign this to someone, make it easy for the team lead to approve: surface each candidate’s current PRs and on-call status, show how long the fix will likely take, and flag risks that would require a different owner or an escalation to Slack #infra.
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
+Issue 4821 needs an owner. Marco has recent context but has three open PRs; Lina is on-call this…
Decide — diagnose the stuck moment
+I need to hand issue 4821 to someone but I'm not sure who is free.
Issue 4821 needs an owner. Marco has recent context but has three open PRs; Lina is on-call this week. I am worried assigning Marco will block him and delay triage, but assigning Lina might interrupt incident handling. Given these constraints, who should I assign now and what note should I add to manage expectations?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across the last two sprints I keep assigning bugs to whoever last touched the file, and they often…
Become — change the pattern
+I repeatedly assign issues to busy people and they miss SLAs.
Across the last two sprints I keep assigning bugs to whoever last touched the file, and they often have five open PRs. That pattern creates delays and resentment. What specific habit or lightweight checklist should I adopt so I pick an owner who can actually deliver within the sprint?
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.