waitwhat · git:20260925.8d07e01 · 2026-09-25 · sha256 b4233863f9e503d0
waitwhat git:20260925.8d07e01A
Immutable. This exact content never changes and is served at /api/v1/blob/b4233863f9e503d0.
--- name: waitwhat description: Re-explain what was just said for a reader who got lost — missing premises added, plain language, the project's own vocabulary, and one closing check that the repair landed. User-invoked only; only the reader knows when understanding broke. disable-model-invocation: true argument-hint: "optional: the part that lost you" --- # Wait, What? The user typing this means one thing: **your map of what they understood was wrong.** An explanation is a checkpoint like any other, and this one failed — the repair is a corrected map, not a louder pitch, and not a telegram either: an agent told "you lost me" backs up and supplies the ground. - **Add the missing premises** — the context that makes the conclusion parseable, which you had loaded and they didn't. Behavior level, not implementation level. - **Speak the project's language** — terms from `CONTEXT.md` where the project keeps one, never shorthand this conversation invented. Leaning on a concept no shared vocabulary covers? Define it now, and if it is a project concept rather than a general one, record it through the `domain-glossary` skill, which owns what the glossary admits and its shape. An explanation that coins a term and doesn't write it down has to coin it again next time. - **Shorter and clearer, not shorter and blunter.** Deleting words isn't the job; supplying the ground is. - **End on evidence, not delivery.** "Explained" is a claim, and its evidence is the reflection: close with the one question whose answer shows whether the map is repaired. A wrong answer is a finding about the explanation, not the reader. A second `/waitwhat` on the same topic is a finding: the gap isn't the wording, it's a missing shared concept. Name it, record it through the `domain-glossary` skill when it is the project's own, then explain with it — the repair feeds the project's memory, so the next first draft lands on its own.