The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Download the full transaction history for the last quarter, including charges, refunds, and fees.…
Execute — do the immediate task
+Download the full transaction history for the last quarter, including charges, refunds, and fees. Start with May 1 through July 31. Export a CSV with columns for transaction ID, date, customer email, gross amount, fee amount, net amount, and refund status. Send the file to devops@ourco.com and finance@ourco.com and confirm the CSV opens correctly in Excel before you finish.
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 export transactions, make the CSV useful for reconciliation. Put a column that shows…
Improve — make it easier to accept
+Before I export transactions, make the CSV useful for reconciliation. Put a column that shows linked invoice numbers, mark refunded transactions clearly with refund IDs next to original charges, and include a fee breakdown column so finance can map fees to merchant accounts. Flag any transactions over $5,000 and any chargebacks for quick review.
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 pulled the quarter’s transactions and saw a cluster of refunds in June totaling $18,400 that I…
Decide — diagnose the stuck moment
+The transaction export shows unexpected refunds
I pulled the quarter’s transactions and saw a cluster of refunds in June totaling $18,400 that I didn’t expect. I don’t know if they’re customer-initiated disputes, automated refunds from a buggy endpoint, or one-off mistakes from support. What steps should I take right now to diagnose the source, which logs or people should I contact first, and how do I freeze further refunds until we confirm the cause?
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 time I hand off transaction exports to accounting they ask for extra columns, or we find…
Become — change the pattern
+Exports keep missing the data fields we need for accounting
Every time I hand off transaction exports to accounting they ask for extra columns, or we find unmapped fees and spend hours patching CSVs. What one change to how we structure and validate transaction exports will stop this repetitive back-and-forth and make reconciliations a one-pass job?
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.