The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+A reviewer resolved a thread about the scope section but the legal team says it was premature. Open…
Execute — do the immediate task
+A reviewer resolved a thread about the scope section but the legal team says it was premature. Open the file, find unresolved comments, and for each one flagged by Legal add a reply summarizing Legal's objection, unresolve the thread so it shows as open, and notify Priya in Legal and the procurement lead, Marcus, asking for a single-line confirmation by Thursday noon.
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 resolving comments in files, make it easier to trust the resolution: show the original…
Improve — make it easier to accept
+Before resolving comments in files, make it easier to trust the resolution: show the original comment, the resolving reply, and the evidence that supports it (version where change occurred or a quoted clause). Highlight any comment resolved without a named approver, and mark those for recheck. Recommend wording that will let Legal approve a resolution in one phrase.
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 resolved several comment threads after what seemed like final edits, then Legal pushed back…
Decide — diagnose the stuck moment
+I clicked resolve but Legal says it's not fixed.
I resolved several comment threads after what seemed like final edits, then Legal pushed back saying the wording still exposes risk. I don't know if I missed wording or if Legal changed their standard. Should I reopen the threads and ask for exact line edits, or pull Legal into a quick call? Which will stop repeated reopenings without wasting Legal's time?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over the last three projects we keep resolving comment threads only to have Legal reopen them,…
Become — change the pattern
+We repeatedly mark comments resolved then get reversals from Legal.
Over the last three projects we keep resolving comment threads only to have Legal reopen them, costing two days each time. Where is our handoff failing — author clarity, Legal's gating criteria, or notification timing? Recommend one checklist item and one notification change to stop these reversals.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other file storage work people do in Google Drive.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.