Create an event or meeting note

Create an event or meeting note in Slack — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

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

Execute — do the immediate task

+
Create a meeting note in #eng-ops for tomorrow's incident review at 11:00 AM. Include an agenda:…
Create a meeting note in #eng-ops for tomorrow's incident review at 11:00 AM. Include an agenda: one-line incident summary, timeline review, action items, and owners. Save the note to the project notes and notify the two incident leads to join and prepare logs.

Improve — make it easier to accept

+
Before I post the meeting note to #eng-ops, make it easy for participants to contribute: put the…
Before I post the meeting note to #eng-ops, make it easy for participants to contribute: put the incident summary at the top, add clear sections for timeline entries, pre-fill three likely action items with owners to confirm or edit, and attach the relevant log links and the postmortem template. Flag any missing data that will block a useful review.

Decide — diagnose the stuck moment

+
I scheduled the incident review for tomorrow but when we do this people often show up without logs…

We called an incident review but people arrive unprepared

I scheduled the incident review for tomorrow but when we do this people often show up without logs or clear timelines. Claire and Daniel expected me to prepare a first draft. I'm worried the meeting will become finger-pointing rather than fixing. I cannot force everyone to prepare. What is the minimal meeting note or prep I should deliver now so the review stays productive and focused on action?

Become — change the pattern

+
Across several incidents, reviews become long and unproductive because people never bring timelines…

Incident reviews drag because prep is inconsistent

Across several incidents, reviews become long and unproductive because people never bring timelines or data. That costs us engineer time and delays fixes. What repeatable practice should I embed into our incident review workflow so prep becomes automatic and meetings finish with clear, owned actions?

Next to this one

Other team chat work people do in Slack.

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.