The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Create a new card titled 'Sprint QA checklist' and populate its checklist from the 'Release QA…
Execute — do the immediate task
+Create a new card titled 'Sprint QA checklist' and populate its checklist from the 'Release QA template' we use. Put the card in the QA list for this sprint, assign it to Lena and Sam, and set the checklist items to be unchecked. Add a comment that says which template you used and who should verify it before the sprint ends.
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 generate a card checklist from our release template, adapt it to this sprint's scope:…
Improve — make it easier to accept
+Before I generate a card checklist from our release template, adapt it to this sprint's scope: remove any steps that don't apply (automation smoke, external vendor signoff), reorder items so critical tests are first, and surface the estimated time per step. Highlight anything that would make a reviewer pause.
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 created a 'Sprint QA checklist' from the release template but several items are irrelevant…
Decide — diagnose the stuck moment
+I applied the template but half the items don't apply this sprint
I created a 'Sprint QA checklist' from the release template but several items are irrelevant because we skipped regression and dropped vendor integration. I'm worried testers will waste time. What's the quickest way to trim and signal which checklist items are out-of-scope so QA focuses correctly?
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 sprint we paste the full release template and testers complain about irrelevant items. Where…
Become — change the pattern
+We keep copying large template checklists and wasting tester time
Every sprint we paste the full release template and testers complain about irrelevant items. Where should we change habit — template design, sprint planning, or ownership of checklist tailoring — and what one practice will stop this waste? Give a 3-line action to implement before the next 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 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.