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 must produce a quality-review sheet for 120 finished units this afternoon. Use the inspection…
Execute — do the immediate task
+I must produce a quality-review sheet for 120 finished units this afternoon. Use the inspection checklist column I paste from the shop, compute pass/fail per item, tally the defect categories, and produce a printable summary with overall pass rate and top three defect types for the QA lead to sign off before batch release.
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 the QA sheet to production, make it faster to use and harder to mis-enter. Move the…
Improve — make it easier to accept
+Before I hand the QA sheet to production, make it faster to use and harder to mis-enter. Move the overall pass/fail to the top so the inspector can see it immediately, show the three most common defect codes per inspector on the summary, add dropdowns for defect codes, and flag any inspector with an unusually high fail rate compared with their monthly average.
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
+During today's run, Sam reported a spike in scratch defects on unit assemblies. I don’t know if…
Decide — diagnose the stuck moment
+An inspector reported a sudden rise in one defect code
During today's run, Sam reported a spike in scratch defects on unit assemblies. I don’t know if Sam’s entries reflect a real process issue, misclassification, or if he selected the wrong defect code in the rush. I’m worried the production manager will stop the line unnecessarily. What quick checks distinguish operator-entry error from a true quality degradation, and how should I present the evidence so the manager can decide to pause or keep running?
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 shift change we reconcile inconsistent defect codes, late entries, and different inspector…
Become — change the pattern
+We spend hours fixing inconsistent inspection records after each shift
Every shift change we reconcile inconsistent defect codes, late entries, and different inspector standards. That wastes time and blurs trends. Recommend one change to how inspections are recorded and one validation we should add to the workbook so daily reconciliation drops from hours to minutes and trend signals become trustworthy.
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.
Category ManagerProcurement ManagerQuantity SurveyorCrowd Management SupervisorProduction Supervisor Chemicalsalso: Ensure quality of final productalso: Inspect quality of products
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.