The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Compile the climate policy analysis brief for the policy director and the advocacy lead: merge…
Execute — do the immediate task
+Compile the climate policy analysis brief for the policy director and the advocacy lead: merge emissions projections, policy scenario inputs, and sensitivity runs into one workbook, rank the policy options by net emissions impact and economic cost, and write a two-paragraph executive summary that states the recommended option and the confidence level. Deliver by Wednesday noon after checking all scenario formulas.
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 sending the model to the advocacy team, make it easy to approve: put the headline emissions…
Improve — make it easier to accept
+Before sending the model to the advocacy team, make it easy to approve: put the headline emissions and cost trade-off up front, provide an uncertainty band for the central estimate, call out any strong assumptions that would make a reviewer hesitate (carbon price path, technology uptake), and include a one-row summary that policy wonks can paste into a memo.
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 re-ran the policy scenarios and the 2035 emissions under our preferred package rose contrary to…
Decide — diagnose the stuck moment
+The scenario that looked safe now shows higher emissions in 2035
I re-ran the policy scenarios and the 2035 emissions under our preferred package rose contrary to expectations. The policy director and two external partners will see this soon; I don't know whether the change came from an input tweak, a model bug, or a real sensitivity to a single assumption. What sequence of checks should I run immediately and what interim message do I send to the partners to keep trust without overcommitting?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Decision makers keep reversing endorsements because our briefs later reveal hidden sensitivities,…
Become — change the pattern
+Our briefs repeatedly provoke last-minute policy reversals
Decision makers keep reversing endorsements because our briefs later reveal hidden sensitivities, creating missed opportunities and reputational damage. The pattern points to poor uncertainty communication and buried assumptions. Which one habit should I change first — require a sensitivity table in every brief, standardize a one-line confidence statement, or hold a short pre-brief with key decision makers — to reduce reversals? Recommend the single change and how to implement it for the next policy memo.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Where the evidence lives
Who was seen doing this, and what people really ask.
Software tasks in the LLOS Work Atlas come from evidence, never a feature list: careers attested to do the work, real job descriptions, and the questions people actually ask (with their view counts). Facets — feature, workflow, troubleshoot, administer, deploy, scale — are open metadata: the work decides, not a taxonomy.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.