The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I need to review what happened with our live API calls for the last 48 hours. Pull the request logs…
Execute — do the immediate task
+I need to review what happened with our live API calls for the last 48 hours. Pull the request logs for production, show me failed requests first, include timestamp, endpoint, HTTP status, response time, and the request ID so I can trace them. Highlight any spikes in 5xx errors and any recent deployments within that window. Ladder":"L1"
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 this to the engineering lead, make the logs easy to triage: surface error rate and…
Improve — make it easier to accept
+Before I hand this to the engineering lead, make the logs easy to triage: surface error rate and latency at the top, group requests by endpoint and request ID, show the top 10 slowest requests with full payload size and response codes, and flag any patterns tied to a deploy or a config change. Ladder":"L2"
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
+In production we just saw the 500 error rate climb from 0.2% to 4% over 20 minutes. The incidents…
Decide — diagnose the stuck moment
+I just saw a sudden jump in 500s.
In production we just saw the 500 error rate climb from 0.2% to 4% over 20 minutes. The incidents touch the /charges and /webhooks endpoints and users report timeouts. I do not know whether it’s our client code, a recent deploy, or an upstream outage. What’s the most likely cause and what are the immediate actions I should take to contain user impact and gather evidence for a rollback or patch? Ladder":"L5"
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 repeatedly waste engineering time chasing noisy API logs after production incidents. We want a…
Become — change the pattern
+Spending hours digging logs after incidents.
We repeatedly waste engineering time chasing noisy API logs after production incidents. We want a routine that catches real regressions faster and avoids firefighting every spike. Recommend a small set of alerts, log views, and ownership rules that stop the 2–3 hour scramble: what to monitor, who acknowledges within 15 minutes, and what evidence to collect before deciding to roll back. Ladder":"L6"
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.