The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Add a new list to the Acme Website board titled Blocked, place it between In Progress and Code…
Execute — do the immediate task
+Add a new list to the Acme Website board titled Blocked, place it between In Progress and Code Review, give it a short description: ‘Use when a card is waiting on external input — tag who blocks it’, and create a Blocked label that automatically applies when a card is moved there.
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 add the Blocked list, make it clear when to use it. Put the list between In Progress and…
Improve — make it easier to accept
+Before I add the Blocked list, make it clear when to use it. Put the list between In Progress and Code Review, add the description ‘Tag the person blocking this and expected unblock date’, add an automation to add the Blocked label and assign the card to the reporter when moved there, and show a visible alert if a card stays blocked more than 48 hours.
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
+A developer just dragged a card into Blocked and left the description empty; the reviewer is upset…
Decide — diagnose the stuck moment
+Someone moved a card to Blocked without explaining why.
A developer just dragged a card into Blocked and left the description empty; the reviewer is upset because there’s no unblock info. I don’t know who is actually blocking or whether this is a genuine external dependency. What’s the likely cause and what precise next step should I take to get the unblock reason and next date without escalating needlessly?
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 few sprints the Blocked list fills up and stays there; tasks rot and people stop using it. It…
Become — change the pattern
+Blocked list becomes a graveyard with no follow‑up.
Every few sprints the Blocked list fills up and stays there; tasks rot and people stop using it. It costs us visibility and kills momentum. Which habit around tracking block reasons, ownership, and review cadence should I adopt so blocked items get resolved or re‑prioritized within 48 hours?
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.