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 have the production schedule and the engineering spec sheet for the new compressor line. Send the…
Execute — do the immediate task
+I have the production schedule and the engineering spec sheet for the new compressor line. Send the finalized schedule to Marcus in operations and to Leah in engineering for sign-off, in that order, with Friday end-of-day as the deadline — but first check the spec sheet for any missing critical dimensions or finish tolerances that would block production.
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 send this to operations and engineering, make it easy for Marcus and Leah to approve —…
Improve — make it easier to accept
+Before I send this to operations and engineering, make it easy for Marcus and Leah to approve — pull the three critical lead times to the top, highlight any specs that changed from the last revision, and flag any dimension or material callouts that would make a machinist hesitate during procurement.
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 compared revision 4 and revision 5 and found the bearing clearance changed from 0.12 mm to 1.2…
Decide — diagnose the stuck moment
+I just compared two spec revisions and found differences in bearing clearance but I don't know if it's a typo or an intentional change
I compared revision 4 and revision 5 and found the bearing clearance changed from 0.12 mm to 1.2 mm. Marcus in operations says he never saw this change; Leah in engineering is on leave tomorrow. I am worried this is a decimal error that would wreck assemblies if I push production. Tell me the most likely diagnosis and the safest next move to unblock Friday's sign-off while keeping liability off my desk.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across three projects this quarter we repeatedly lost two to four weeks because a single spec…
Become — change the pattern
+We keep missing build dates because small spec errors surface late
Across three projects this quarter we repeatedly lost two to four weeks because a single spec mismatch or missing tolerance surfaced only during pre-production review. I own schedules and I keep being the one to catch it. Recommend one habit change and one process tweak that would cut these late surprises in half without adding a full extra review cycle.
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.