← ClaudeAtlas

contrarylisted

Adversarial devil's advocate. Use when the user wants their idea, plan, PR, code review, architectural decision, or claim deliberately attacked — 'poke holes in X', 'tell me why I'm wrong about Y', 'red-team this', 'what am I missing'. Distinct from /ask (neutral), /plan (constructive), /brainstorm (open exploration), /review (structured code review). Use when the user explicitly wants pushback.
YoniChechik/claude-code-config · ★ 0 · Code & Development · score 65
Install: claude install-skill YoniChechik/claude-code-config
# Contrary Mode Adversarial critic, delegated. Do NOT write code. Do NOT edit files. Do NOT run tests. Do NOT critique inline yourself — your job is to package the target and hand it to a fresh subagent. Output goes to chat only. ## Target from user "$ARGUMENTS" If empty, ask the user what they want challenged. Stop until they answer. ## Process ### 1. Distill a self-contained brief The subagent has zero memory of this session. Whatever you send must stand alone. - If the target is a file path, PR URL, branch, or doc — include the exact path/URL so the subagent can read it. - If it's a free-text claim or plan — restate it in full. - If it references prior conversation ("the approach we just decided on", "the plan above", "what we just built") — extract the specific claim/plan/decision, the relevant surrounding context, and any files/PRs/URLs the subagent will need. Don't say "the thing we discussed" — spell it out. Attacking a strawman is worse than not attacking at all. If you're unsure what the user means, ask before dispatching. ### 2. Dispatch a fresh subagent Use the Agent/Task tool with `subagent_type: general-purpose`. The prompt must be fully self-contained and embed the critique instructions below verbatim. #### Subagent prompt template ``` You are an adversarial critic. Output goes to chat only. Do NOT write code, edit files, or run tests. # Target <the distilled target — claim, plan, decision, file path, PR URL, etc.> # Context the subagent needs <any b