The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Invite people to the Riverside Bakery Summer Block Party: send invites to our customer list of…
Execute — do the immediate task
+Invite people to the Riverside Bakery Summer Block Party: send invites to our customer list of 1,200 emails, select the RSVP button, invite the 320 people who marked 'interested' at last summer's event, and message the Elm Street Neighborhood Association contact list. Make sure not to invite vendors whose contracts are pending. After sending, confirm the invite count and log which 10 VIP customers got personal messages from Marcus.
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 hit invite for the July 22 block party, make the RSVP flow easier for busy locals: surface…
Improve — make it easier to accept
+Before I hit invite for the July 22 block party, make the RSVP flow easier for busy locals: surface the RSVP button at the top of the event page, prepare a short invite message that mentions free samples and a 20% coupon, filter out vendors with pending contracts so they don't get a public invite, and flag any privacy settings or audience caps that would stop our 1,200-customer list from receiving invites.
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 just sent invites to our full customer list for July 22; afterward Marcus said three vendors…
Decide — diagnose the stuck moment
+I clicked invite for 1,200 but some vendors weren't supposed to be invited.
I just sent invites to our full customer list for July 22; afterward Marcus said three vendors still have pending contracts and shouldn't have received public invites. I don't know whether I can retract those invites or how this will affect vendor negotiations. What is the likely fallout and the quickest remedy to limit damage with the vendors and with our public invite list?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We keep sending event invites to vendors or partners by mistake, causing awkward contract…
Become — change the pattern
+We repeatedly invite the wrong segment and then have to retract.
We keep sending event invites to vendors or partners by mistake, causing awkward contract conversations and extra work removing them from RSVPs. Where is the recurring failure — poor audience tagging, too-fast invite steps, or lack of a vetting checklist — and what one operational habit will stop these wrong invites before they go out?
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 social platform work people do in Facebook.
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.