The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Move the card ‘UX testing feedback’ from In Review to Backlog. Leave a comment explaining why:…
Execute — do the immediate task
+Move the card ‘UX testing feedback’ from In Review to Backlog. Leave a comment explaining why: tests were inconclusive and we need another round. Tag Alex so he knows it’s de-prioritized and won’t be expected in the current sprint.
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 move ‘UX testing feedback’ back to Backlog, make it clear to reviewers why: summarize…
Improve — make it easier to accept
+Before I move ‘UX testing feedback’ back to Backlog, make it clear to reviewers why: summarize outstanding questions, show the most recent test results under the heading ‘Why not ready’, and flag any dependencies so the reviewer won’t be surprised by the change.
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 moved ‘UX testing feedback’ from In Review to Backlog because results were weak, and the product…
Decide — diagnose the stuck moment
+I dragged a card back to Backlog and the product manager reacted badly.
I moved ‘UX testing feedback’ from In Review to Backlog because results were weak, and the product manager pushed back saying scope creep. I don’t know if I should have archived the card or created a duplicate for retesting. What’s the best next move to keep transparency and avoid scope fights?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Cards are frequently shuffled between lists mid-sprint and teammates complain they weren’t…
Become — change the pattern
+Cards move between lists without explanation and create confusion.
Cards are frequently shuffled between lists mid-sprint and teammates complain they weren’t informed, which erodes trust. What habit or short protocol should I introduce so moves are accompanied by a clear reason and notification that preserves sprint integrity?
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.