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 send the joint-communication draft on the irrigation pilot to Priya at the State Water…
Execute — do the immediate task
+I need to send the joint-communication draft on the irrigation pilot to Priya at the State Water Board and to Ahmed at the District Planning Office for sign-off this Friday. Read the attached memo, make sure the agency names, boundaries and timelines match the joint memorandum of understanding from last month, then send to Priya and Ahmed in that order with a one-line cover saying this needs signature by Friday or we cannot release seed purchases.
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 circulate the stakeholder brief to the village council, make it quick to approve: put the…
Improve — make it easier to accept
+Before I circulate the stakeholder brief to the village council, make it quick to approve: put the key request — approval for two irrigation sites and a 30% co-funding ask — at the top, show the deadline and funding source on the front page, and highlight any items likely to trigger procurement queries so I can pre-answer them.
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
+Two district engineers have sent different boundary maps for the pilot area and we must pick one to…
Decide — diagnose the stuck moment
+We just received conflicting boundary maps from two district engineers.
Two district engineers have sent different boundary maps for the pilot area and we must pick one to include in the joint letter to the State Water Board by Friday. I am worried choosing the wrong map will delay approvals and anger the district planning office; I cannot tell whether either engineer will accept corrections. Recommend the likely safer map to use, the one-line justification I should put in the cover email, and the fastest way to confirm with minimal back-and-forth.
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 project cycle, last-minute map updates force rework of the joint memo and delay procurement…
Become — change the pattern
+We keep getting last-minute map corrections from districts.
Every project cycle, last-minute map updates force rework of the joint memo and delay procurement by days. I need a habit that prevents this scramble. Recommend a concrete change to my intake and review steps — who to ping, what map versioning and sign-off language to require, and a short template for the cover email that gets districts to confirm or flag changes within three working days.
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.