Stop. That last message did not land. Re-pitch it: back up as far as needed, add the context that was missing, write in ASD-STE100 Simplified Technical English, and use the project's own ubiquitous language. Type /discipline:wait-what the moment you notice you are skimming; only you know when you stopped following.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add melodic-software/claude-code-plugins --skill wait-what --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Wait What?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/melodic-software-wait-what)More formats (shields.io, HTML) on the badges page.
---
description: "Stop. That last message did not land. Re-pitch it: back up as far as needed, add the context that was missing, write in ASD-STE100 Simplified Technical English, and use the project's own ubiquitous language. Type /discipline:wait-what the moment you notice you are skimming; only you know when you stopped following."
user-invocable: true
disable-model-invocation: true
metadata:
workflow-stage: anytime
summary: Re-pitch the message that did not land. Missing context added, plain register, project vocabulary
---
# Wait. What?
Wait. I don't understand where you've got to here. Re-pitch that: back up as
far as needed, give me the context I was missing, talk in ASD-STE100
Simplified Technical English (short sentences, one meaning per word, technical
terms exact), and use the project's ubiquitous language. Read the nearest
domain glossary or context map, per the project's own convention, when one
exists; with none, plain technical English alone.
## A declared species in this plugin: NOT a corrector
Every sibling corrector re-anchors a standing discipline through the
re-anchor/audit/correct loop. This skill is a one-shot, user-fired
communication repair: the human, the only party who can detect that a message
did not land, fires it, and the re-pitch IS the repair. It deliberately stays
this small: a skill that fights unclear output fails by growing, because the
model reads the volume, not the plea. Nearest siblings, for routing:
`/discipline:tighten-your-output` when the problem is too many words, and
`/discipline:mind-your-maxims` when the standing cooperative-communication
discipline itself needs re-anchoring; this skill repairs the one message that
lost its reader.
## Boundaries
- **Never model-invoked.** `disable-model-invocation: true` is load-bearing:
the model cannot detect that its reader stopped following, so an
auto-fired re-pitch would be incoherent.
- **Re-pitch means re-ground, not compress.** Full technical precision stays;
the premise the reader was missing comes back. A re-pitch that is shorter
and blunter, but no clearer, is the failure this skill exists to avoid.
- **No glossary is a no-op, not an error.** The vocabulary half degrades
silently; the register and missing-context halves always apply.
- **Excluded from batch sweeps.** No `discipline-batch` tier on purpose: a
sweep must never fire a repair only the human can call for.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!