菜单
Devil's advocate thinking mode. Surfaces real misconceptions in the user's position, starting with the strongest objection. Use when the user asks to "prove me wrong", "challenge my thinking", "what am I missing", "play devil's advocate", "poke holes in this", "what's wrong with my reasoning", or uses the /pmw command.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | prove-me-wrong |
| description | Devil's advocate thinking mode. Surfaces real misconceptions in the user's position, starting with the strongest objection. Use when the user asks to "prove me wrong", "challenge my thinking", "what am I missing", "play devil's advocate", "poke holes in this", "what's wrong with my reasoning", or uses the /pmw command. |
| version | 0.1.0 |
Devil's advocate mode: find the strongest case against the user's position.
Stop when you've run out of real objections. Say so explicitly:
"I don't have a stronger objection than what we've already covered."
The user can say something like "keep going" to push further.
Never nitpick. If the next candidate is about wording, minor edge cases, or implementation detail rather than a genuine flaw in the reasoning — stop. Around five objections is typically the ceiling before quality degrades into noise.
The user can also exit the mode at any time by saying something like "ok, I'm convinced", "stop", or "let's move on".
Always load this skill when working on a Quarkus project, when the quarkus-maven-plugin is present in pom.xml, or when project setup has already chosen Quarkus before the pom.xml exists yet. It provides Quarkus-specific patterns and gotchas that complement the java and maven skills.
Orchestrator role in the Unfolding Specs process. Launches the PO, forwards unsolicited Sensei guidance, handles genuine commissioner issues, and resumes the workflow through the platform-specific live task mechanism.
Always load this skill when a pom.xml file exists in the project, when creating or editing a pom.xml, or when setting up Maven project structure in a new project. It provides Maven-specific conventions for running tests, building, managing dependencies, and project structure.
This skill should be used when starting work on any project that uses tdder. It establishes interaction style, commit conventions, documentation discipline, and skill-trust principles. Invoke automatically alongside other tdder skills.
Always load this skill when writing, modifying, creating, or moving Java or Kotlin source code, or when project setup has already chosen Java/Kotlin as the implementation language.
This skill should be used when the user asks to "add a feature using TDD", "fix a bug with TDD", "do TDD", "red-green-refactor", "write a failing test first", "use test-driven development", "start TDD", "test first approach", "TDD loop", "TDD cycle", or mentions TDD workflow, baby steps, guessing game, or red-green-refactor cycles. Not applicable for pure refactoring without new tests.
