Monitor soil conditions and crop health

Monitor soil conditions and crop health — real work, not an imagined feature: named inside 8 evidenced career tasks. Below are four ready AI prompts for it, one per height of help: do it, make it easier to accept, decide when you are stuck, and change the pattern for good.

8career tasks name it
4prompt heights

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
Send the soil and crop monitoring workbook to Priya in agronomy and to Luis, the field manager, for…
Send the soil and crop monitoring workbook to Priya in agronomy and to Luis, the field manager, for sign-off, in that order, with a Friday close. Before sending, verify the sensor data imports into the latest daily sheet, ensure the NDVI chart shows the last two weeks, and confirm conditional alerts flag fields 3B and 7A.

Improve — make it easier to accept

+
Before I hand this to field operations, make the workbook easy to act on: put critical alerts and a…
Before I hand this to field operations, make the workbook easy to act on: put critical alerts and a one-line recommendation for each field on the dashboard, make soil moisture and NDVI trends findable within two clicks, and highlight any calibration gaps that would make a farm manager hesitate to trust the numbers.

Decide — diagnose the stuck moment

+
The agronomy team says irrigation was automated; the field manager says no irrigation ran. The…

Field sensors show a sudden drop in moisture for blocks 3B and 7A.

The agronomy team says irrigation was automated; the field manager says no irrigation ran. The sensor time series shows a step change at 03:00 but the logger reports no comms errors. I cannot tell whether the sensors failed, irrigation control failed, or a real leak happened. What is the likely diagnosis and the immediate next check I should ask Luis to perform before we alert the growers?

Become — change the pattern

+
Across the last six monitoring cycles we waste hours reconciling sensor drops and filling gaps…

We repeatedly chase sensor anomalies and re-run cleaning scripts before every planning meeting.

Across the last six monitoring cycles we waste hours reconciling sensor drops and filling gaps manually. Where am I losing time and risking wrong recommendations, and what one change in data validation or reporting would cut that work out of the routine?

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.