The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Update billing details for Hannah Lee’s subscription to the new card ending 3421 and copy Marcus in…
Execute — do the immediate task
+Update billing details for Hannah Lee’s subscription to the new card ending 3421 and copy Marcus in billing. Make the change effective immediately so the next recurring charge goes to the updated card and confirm by email once successful.
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 send the billing-update link to a customer, make it easy for the reviewer: show the…
Improve — make it easier to accept
+Before I send the billing-update link to a customer, make it easy for the reviewer: show the current saved payment method, the date it expires, any failed payment history, and surface whether updating will retry a previously failed charge so the support rep can approve sending the link without extra back-and-forth.
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 customer sent a new card number in chat after two failed charges. I know we must not store card…
Decide — diagnose the stuck moment
+Customer’s card failed and they supplied a new card number over chat.
A customer sent a new card number in chat after two failed charges. I know we must not store card numbers in chat and I’m worried about triggering duplicate charges or chargebacks if I update the method wrong. What exact steps should I take right now to replace the payment method securely, schedule a retry if appropriate, and document the change for finance and the client?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We keep manually updating cards after failed payments, and often forget to schedule a retry or…
Become — change the pattern
+We handle many manual card updates and miss retries on failed charges.
We keep manually updating cards after failed payments, and often forget to schedule a retry or record who authorized the change, causing lost revenue and disputes. Which habit will stop this: forcing customers to update via a secure hosted payment page only, automated retry rules, or a mandatory logged approval step? Recommend one change, the implementation steps, and how to train support on it this month.
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 payments work people do in PayPal.
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.