The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Investigate the payment failure spike for transaction batch on July 14. Pull failed charge logs,…
Execute — do the immediate task
+Investigate the payment failure spike for transaction batch on July 14. Pull failed charge logs, list error codes for 120 failed attempts from customer portal checkouts, and group them by failure reason: insufficient_funds, incorrect_cvc, authentication_required, processing_error. Narrow the top three offending payment methods and provide the raw error rows so developers can reproduce one failure locally.
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 hand the failure log to engineering, make the incident easy to fix. Summarize the top five…
Improve — make it easier to accept
+Before I hand the failure log to engineering, make the incident easy to fix. Summarize the top five error codes for the July 14 spike, show the percentage of failed attempts per merchant region and browser, and flag which failures are client-side (card entry) versus gateway-side. Recommend one targeted alert we could add so developers see the pattern immediately next time.
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
+We saw a sudden doubling of payment failures at 10:12am and the finance lead, Omar, is demanding a…
Decide — diagnose the stuck moment
+A backlog of payment failures just doubled and I don’t know which are real declines
We saw a sudden doubling of payment failures at 10:12am and the finance lead, Omar, is demanding a root cause. The logs show a mix of incorrect_cvc and processing_error codes; I can’t tell which are true card declines and which are gateway hiccups. I’m afraid we’ll escalate the wrong fix to engineering. What is the most likely split and what specific log check will tell me in the next 30 minutes?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Our team spends hours every month firefighting short-lived payment failure spikes that waste…
Become — change the pattern
+We repeatedly chase transient gateway errors instead of fixing the root cause
Our team spends hours every month firefighting short-lived payment failure spikes that waste developer cycles and leave true decline trends unnoticed. Where are we mismeasuring failures, and what one structural change to logs or alerts would stop us from chasing noise and instead surface real problems?
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 Stripe.
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.