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 deliver the tested batch results to Simon in quality and to Claire in product engineering…
Execute — do the immediate task
+I need to deliver the tested batch results to Simon in quality and to Claire in product engineering for sign-off by Wednesday. Confirm each sample row shows test ID, pass/fail status, measured value with units, the test method reference, and that the acceptance criteria sheet links correctly to the reported results.
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 test-results workbook, make it easy for reviewers to pick the important…
Improve — make it easier to accept
+Before I circulate the test-results workbook, make it easy for reviewers to pick the important failures: surface the overall pass rate and the three worst-performing parameters at the top, group failures by root-cause suspected, and highlight any results that fall just inside tolerance which an engineer might still reject.
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 recalculated the test worksheet and one critical tensile test changed from pass to fail. The…
Decide — diagnose the stuck moment
+a key test toggled from pass to fail after recalculation.
I recalculated the test worksheet and one critical tensile test changed from pass to fail. The engineering lead asked for an explanation and the production run waits on approval. I don't know whether the recalculation used updated calibration factors or an overwritten acceptance threshold. What is the most likely reason, what quick checks should I run now, and what should I tell Claire while I investigate?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Test reports keep flipping status because acceptance thresholds are adjusted late by engineering,…
Become — change the pattern
+results are often reclassified after late threshold changes
Test reports keep flipping status because acceptance thresholds are adjusted late by engineering, forcing rework and delaying approvals. Where are we losing accuracy and trust, and what two changes to how thresholds are set, versioned, and communicated would prevent future surprises?
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.
Quality Control ApparelQuality Control Food ServiceQuality Control InspectorComputer EngineerDesign Systems DesignerCalibration Technicianalso: Record and analyze test dataalso: Analyze test data to identify defectsalso: Compile and analyze test results
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.