Track loose ends with Awaiting

Keep a question or commitment visible until it is actually resolved.

Record the next move

An Awaiting item belongs to a thread. It describes what remains open, whether the next move is yours or someone else’s, and an expected completion date when one is useful.

Add an Awaiting item: I need to choose the onboarding approach after
reviewing out/proposed-changes.md. The next move is mine.

Use a specific decision or expected result. “Waiting for Sam to approve the copy” is more useful than “follow up.”

Review and resolve

Open the thread’s Awaiting items when you return. Check what changed, update the owner or expected date, and resolve an item with a short explanation when the expectation is met.

Mute or snooze an item when it should stop asking for attention for a while. That leaves the loose end open. Resolution means the work or decision is settled.

How it differs from a notification

A notification tells you something happened. An Awaiting item says something still needs to happen. Reading a notification does not resolve the underlying item.

A loop can produce Awaiting items at its checkpoints, and an automation can review them later. Each still has a separate purpose.

Agent example

hai await projects/onboarding '{"id":"choose-approach","op":"set","item":{"desc":"Choose the onboarding approach","direction":"mine","where":"self","status":"open"}}'

Reuse the same item ID when updating it. The set operation replaces that item, so retain the details you want to keep. Resolve with status: "resolved" and a resolution_details explanation. Use the Awaiting skill for ordinary updates.