wait-what
Stop. That last message did not land — re-pitch it.
- License 许可
- MIT
- 最近更新
- 2026-09-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- wait-what
- description
- Stop. That last message did not land — re-pitch it.
- argument-hint
- [which part lost you — optional]
- disable-model-invocation
- true
02 资源文件 1
- 许可证LICENSE-mattpocock-skills1.7 KB
03 SKILL.md 正文
Wait — I don't understand where you've got to here. Re-pitch that: give me a little bit of context, talk in ASD-STE100 Simplified Technical English, and use the ubiquitous language from CONTEXT.md.
04 同仓库更多 Skills
wait-what
Stop. That last message did not land — re-pitch it.
sp-writing-plans
You MUST use this, and not the upstream superpowers writing-plans skill, when you have a spec or requirements for a multi-step task, before touching code. The plan review is a checklist you run yourself, and execution hands off to sp-subagent-driven-development or sp-executing-plans.
sp-subagent-driven-development
You MUST use this, and not the upstream superpowers subagent-driven-development skill, when executing implementation plans with independent tasks in the current session. Dispatched task and whole-branch reviews run the scrutinize-dispatch skill; the re-review is deliberately unrouted.
sp-requesting-code-review
You MUST use this, and not the upstream superpowers requesting-code-review skill, when completing tasks, implementing major features, or before merging to verify work meets requirements. The review itself runs the scrutinize-dispatch skill.
sp-receiving-code-review
You MUST use this, and not the upstream superpowers receiving-code-review skill, when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
sp-executing-plans
You MUST use this, and not the upstream superpowers executing-plans skill, when you have a written implementation plan to execute in a separate session with review checkpoints. Review checkpoints are run in-session by you, not dispatched to a reviewer subagent.