Challenge proposals, designs, plans, or analyses with devil's advocate. Use when user mentions devils advocate, 反論, チャレンジ, challenge, 叩いて, 穴探し. Do NOT use for code review findings (use /audit which has built-in challenger).
From shipnpx claudepluginhub thkt/dotclaude --plugin toolkitThis skill is limited to using the following tools:
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.
Spawn devils-advocate-design against a proposal, analysis, or plan.
$1: what to challenge (description, or file path)$1 is empty: challenge the most recent proposal/analysis in this
conversation| Step | Action | Detail |
|---|---|---|
| 1 | Identify target | Extract from $1 or conversation context |
| 2 | Spawn DA | Task(subagent_type: devils-advocate-design, background: true) |
| 3 | Report | Verdict table + summary metrics + actionable items |
Include the target and any file paths the user referenced. Mention ARCHITECTURE.md or equivalent structural constraint files if they exist in the target project. The agent collects its own context via Read/Grep/Glob.
Present DA results with: