The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+This card needs an honest time estimate before I hand it to the devs. Add an estimate of 3 hours to…
Execute — do the immediate task
+This card needs an honest time estimate before I hand it to the devs. Add an estimate of 3 hours to the card's visible metadata field so everyone sees it on the board, and leave a short comment explaining what that 3 hours includes. Check the card already has acceptance criteria and attach the latest mock if it's missing.
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 publish estimates across the sprint, make this card easy to act on: show the 3‑hour…
Improve — make it easier to accept
+Before I publish estimates across the sprint, make this card easy to act on: show the 3‑hour estimate at the top of the card preview, highlight any missing acceptance criteria, and add a one‑line note that explains whether the 3 hours includes QA and deployment. Flag anything that would make a reviewer hesitate to accept the estimate.
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 wrote a 3‑hour estimate on the card and Priya, the product owner, said it feels low. She wants…
Decide — diagnose the stuck moment
+I just guessed 3 hours but the PO pushed back
I wrote a 3‑hour estimate on the card and Priya, the product owner, said it feels low. She wants justification but I don't have a breakdown. Tell me the most likely reasons my estimate looks low to her and the best next move: suggest a short breakdown to share now, a risk buffer, or ask for a quick grooming session?
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 sprints I repeatedly mark small feature cards with optimistic hours and we miss deadlines. I…
Become — change the pattern
+I keep underestimating similar tasks
Across sprints I repeatedly mark small feature cards with optimistic hours and we miss deadlines. I spend time defending estimates in standups. Diagnose the pattern and recommend one concrete habit change to stop churn and rebuild trust with the product owner within two sprints.
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.