shipshitdev/skills

wait-what

Re-pitch the last message in plain English using the project's CONTEXT.md vocabulary.

First seen Aug 14, 2026

Installation

$ npx skills add shipshitdev/skills --skill wait-what

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from shipshitdev/skills · top by installs.

npx skills add shipshitdev/skills

Browse all from shipshitdev/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 35
License MIT
Default branch master
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
LicenseMIT
More metadata
version
1.0.0
tags
clarification, communication, context, glossary
author
Ship Shit Dev
source
https://github.com/mattpocock/skills/blob/main/skills/productivity/wait-what/SKILL.md
upstream_repo
mattpocock/skills
upstream_ref
main
upstream_commit
8b78b531ab96
last_synced
2026-08-14
license
MIT

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,853 B
  • docs SUMMARY.md 102 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 13 installs

SKILL.md

Wait What

The last message did not land. Re-pitch it.

Contract

Inputs:

  • The immediately preceding assistant message (and enough surrounding turn context to know what it was trying to say)
  • CONTEXT.md / CONTEXT-MAP.md when present

Outputs:

  • A short re-pitch of the same point: missing context filled in, jargon decoded, same conclusion

Creates/Modifies:

  • None

External Side Effects:

  • None

Confirmation Required:

  • None. Advisory only.

Delegates To:

  • domain-modeling only when the confusion is a glossary conflict that should be written down

Re-pitch

  1. Name the point that failed to land, in one sentence.
  2. Add the missing context — the decision, constraint, or prior turn the user did not have.
  3. Speak in plain English. Prefer Simplified Technical English: short sentences, one idea each, no filler.
  4. Use the ubiquitous language from CONTEXT.md when a glossary exists. If a term in the last message is not in the glossary, say the plain-English meaning first, then the canonical term.
  5. End with the same ask or conclusion as the original message, restated.

Do not restart the parent skill. Do not expand scope. This is a mid-conversation corrective; after the re-pitch, the parent flow continues.