wait-what
The reader lost the thread of the previous reply. Explain it again, adding the context they lacked, in ASD-STE100 Simplified Technical English and the project's own domain terms. Type /discipline:wait-what the moment you notice you are skimming; only the reader knows when they stopped following.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 30
- Forks
- 7
01 前言 Front Matter
- metadata
- { "summary": "Re-pitch the message that did not land. Missing context added, plain register, project vocabulary", "workflow-stage": "anytime" }
- description
- The reader lost the thread of the previous reply. Explain it again, adding the context they lacked, in ASD-STE100 Simplified Technical English and the project's own domain terms. Type /discipline:wait-what the moment you notice you are skimming; only the reader knows when they stopped following.
- user-invocable
- true
- disable-model-invocation
- true
03 SKILL.md 正文
Wait. What?
I lost track of your last reply. Go back to the last point I clearly
followed and explain again from there, adding the context I was missing.
Write it in ASD-STE100 Simplified Technical English (short sentences, one
meaning per word, technical terms exact) and use the terms the project
itself uses for its domain. Read its domain glossary with
/domain-driven-design:ubiquitous-language lookup when that skill is available, or
find the glossary yourself, when one exists; with none, plain technical
English alone.
Boundaries
- One-shot repair, not a corrector. It re-pitches the one message that lost its reader and sets no standing posture; the re-pitch is the repair.
- Re-ground, not compress. Full technical precision stays and the missing premise comes back. A shorter, blunter reply that is no clearer is the failure this skill exists to avoid.
- No glossary is a silent no-op, not an error. The vocabulary half drops without comment; the register and missing-context halves always apply.
- Only the reader fires it. The model cannot tell its reader stopped
following, so
disable-model-invocation: truestays and nodiscipline-batchtier is set. - Siblings.
/discipline:tighten-your-outputwhen the problem is too many words;/discipline:mind-your-maximswhen the standing communication discipline needs re-anchoring. If installed,/education:explainwhen the reader needs the idea simplified, not the message re-grounded, and/adhd:clarifywhen the content is right but the shape is wrong.
04 同仓库更多 Skills
track
Backlog reads through the bound tracker: search open and closed items, view one item with its comments and state history. Use when another skill searches or reads tracker items.
reviewer-media
Reviewer media for one pull request: decides whether it needs a narrated walkthrough, builds the storyboard from /review:explain-change's digest, has /explainer-video:produce render it and hands the manifest to /source-control:pull-request media. Use when asked for 'reviewer media', 'a walkthrough video for this PR', 'a produced video of this change', or when pull-request ready or monitor hands a PR over.
route
Model and effort per agent role (orchestrator, worker, verifier, retrieval) for a multi-agent run, resolved through the bundled defaults and the user, team and personal override config layers into fenced JSON with single-agent and fan-out variants and the layer behind each value. Use when asked 'which model for the subagents', 'route the roles' or 'model routing', or before a skill passes a role's model on a spawn.
route
Model and effort per agent role (orchestrator, worker, verifier, retrieval) for a multi-agent run, resolved through the bundled defaults and the user, team and personal override config layers into fenced JSON with single-agent and fan-out variants and the layer behind each value. Use when asked 'which model for the subagents', 'route the roles' or 'model routing', or before a skill passes a role's model on a spawn.
principles
Module-design vocabulary for architecture findings, and the checks built on it. Use when: 'what is a deep module', 'what is a seam', 'deep vs shallow module', 'what is the deletion test', 'leverage and locality', 'module design vocabulary', 'which word do we use for X in architecture findings'. Scanning a codebase for friction is /architecture:improve.
write
Structured five-field bug report (title, steps to reproduce, expected vs actual, justified severity, suggested fix location) from an informal description, read-only. Use when the user names a defect they observed, or asks for one written up ('report a bug', 'file a bug', 'write this up as a bug').