devils-twin

GitHub

模拟最强反对者视角撰写反驳备忘录,评估文档论点强弱,并提供预emptive段落和最终决策建议,帮助在发布前应对真实异议。

skills/devils-twin/SKILL.md mohitagw15856/pm-claude-skills

Trigger Scenarios

文档即将发布且团队意见一致时 需要预判并准备应对关键利益相关者的强烈反对

Install

npx skills add mohitagw15856/pm-claude-skills --skill devils-twin -g -y
More Options

Use without installing

npx skills use mohitagw15856/pm-claude-skills@devils-twin

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill devils-twin -a claude-code -g -y

安装 repo 全部 skill

npx skills add mohitagw15856/pm-claude-skills --all -g -y

预览 repo 内 skill

npx skills add mohitagw15856/pm-claude-skills --list

SKILL.md

Frontmatter
{
    "name": "devils-twin",
    "description": "The strongest possible case AGAINST what you just wrote — argued to win, not to check a box. Use when a document is about to ship and everyone around it already agrees: the twin writes the opposition's best memo (not a critique of yours), so you meet the real counter-argument before your audience does. Produces the opposing memo, the map of which of your claims it defeats\/dents\/leaves standing, and the pre-emption paragraph worth adding."
}

Devil's Twin

Critique finds weaknesses in your argument. The twin does something scarier: it writes the other side's argument, from their premises, at full strength — the memo your smartest opponent would circulate an hour after yours. If your document survives its twin, it will survive the meeting.

Required Inputs

  • The document — full text. The twin argues against the strongest version of what you wrote, so it must see all of it.
  • Who would oppose this in real life (optional but sharpening) — the CFO, the incumbent team, the sceptical customer, the regulator. The twin adopts their premises, not a generic contrarian's.

How the Twin Argues

  • It starts from the opponent's values (their scoreboard, their risks), not from negations of yours — real opposition is a different worldview, not your worldview with "not" inserted.
  • It concedes your strongest point early — sophisticated opponents do; conceding makes the rest of their case credible.
  • It uses your own evidence where possible — the most damaging counter-memos re-read your data and reach the other conclusion.
  • It is written to persuade your shared audience, in the register of your organisation — a memo, not a rant.

Output Format

  1. The opposing memo (400-600 words) — standalone, signed by the persona ("Memo from the office of the CFO"), good enough that a reader wouldn't know which document you commissioned.
  2. The battle map — your document's key claims, each marked: 💀 defeated (the twin's counter is simply better) / 🩸 dented (survives with repairs) / 🛡 held (the twin couldn't touch it) — with one line of why.
  3. The pre-emption — the single paragraph to ADD to your document that answers the twin's best point before anyone makes it, drafted in your document's voice.
  4. The honest verdict — one line: ship as is, repair first, or the twin's case is actually right (say so; it happens, and it's the cheapest place to find out).

Quality Checks

  • The memo argues FROM the opponent's premises — deleting "not" from your claims would not reconstruct it
  • It concedes at least one of your points — full-spectrum opposition is a strawman wearing a suit
  • At least one of your claims is marked 💀 or the twin explains why your case is unusually airtight (rare; suspicious)
  • The pre-emption paragraph is drop-in ready — your voice, your document's structure, no "as some may argue" throat-clearing
  • If the twin's case is stronger overall, the verdict says so plainly

Anti-Patterns

  • Do not write a critique with quotations — the deliverable is the opposition's own memo, structure and all
  • Do not make the twin stupid to make you feel good — a weak twin is worse than none; it inoculates you against the wrong argument
  • Do not have the twin invent facts — it may reinterpret your evidence and add commonly-known context, never fabricate data
  • Do not skip the verdict to stay diplomatic — "repair first" beats a polite shrug
  • Do not use the twin on documents whose audience is hostile already — it's for consensus rooms, where nobody else will say this

Version History

  • 961cbeb Current 2026-07-11 19:41

Same Skill Collection

exports/openclaw/360-feedback-template/SKILL.md
exports/openclaw/401k-plan-decoder/SKILL.md
exports/openclaw/ab-test-planner/SKILL.md
exports/openclaw/ab-test-readout/SKILL.md
exports/openclaw/accessibility-audit/SKILL.md
exports/openclaw/account-plan/SKILL.md
exports/openclaw/acquirer-red-team/SKILL.md
exports/openclaw/ad-copy/SKILL.md
exports/openclaw/aeo-optimizer/SKILL.md
exports/openclaw/agenda-or-cancel/SKILL.md
exports/openclaw/agent-design-review/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/ai-ethics-review/SKILL.md
exports/openclaw/ai-eval-plan/SKILL.md
exports/openclaw/ai-feature-prd/SKILL.md
exports/openclaw/ai-product-canvas/SKILL.md
exports/openclaw/air-quality/SKILL.md
exports/openclaw/altitude-shifter/SKILL.md
exports/openclaw/ambiguity-resolver/SKILL.md
exports/openclaw/analyst-relations-brief/SKILL.md
exports/openclaw/announcement-card/SKILL.md
exports/openclaw/api-docs-writer/SKILL.md
exports/openclaw/api-test-plan/SKILL.md
exports/openclaw/api-versioning-strategy/SKILL.md
exports/openclaw/apology-letter/SKILL.md
exports/openclaw/architecture-decision-record/SKILL.md
exports/openclaw/architecture-diagram/SKILL.md
exports/openclaw/archive-strategy/SKILL.md
exports/openclaw/assumption-bounty/SKILL.md
exports/openclaw/assumption-mapper/SKILL.md
exports/openclaw/async-update-format/SKILL.md
exports/openclaw/auto-repair-estimate-decoder/SKILL.md
exports/openclaw/autopilot-charter/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-minutes/SKILL.md
exports/openclaw/board-pre-read/SKILL.md
exports/openclaw/bom-cost-review/SKILL.md
exports/openclaw/bookkeeping-categorization/SKILL.md
exports/openclaw/boolean-search-builder/SKILL.md
exports/openclaw/brag-doc/SKILL.md
exports/openclaw/brainstorming/SKILL.md
exports/openclaw/brief-builder/SKILL.md
exports/openclaw/briefing-note/SKILL.md
exports/openclaw/budget-builder/SKILL.md
exports/openclaw/budget-variance-analysis/SKILL.md
exports/openclaw/bug-diagnosis/SKILL.md
exports/openclaw/bug-report/SKILL.md

Metadata

Files
0
Version
471c606
Hash
0f752c5f
Indexed
2026-07-11 19:41

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-30 13:07
浙ICP备14020137号-1 $방문자$