devils-advocate

Challenges PRDs and specs with critical questions, failure scenarios, and blind spot analysis.

Updated May 18, 2026
One-click install
npx skills add https://github.com/fahadnari/Claude-skills --skill devils-advocate-fahadnari
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devils-advocate
Source: https://github.com/fahadnari/Claude-skills/tree/main/devils-advocate
Command: npx skills add https://github.com/fahadnari/Claude-skills --skill devils-advocate-fahadnari

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product proposals often ship with untested assumptions, hidden risks, and blind spots that only surface during stakeholder review or after launch. This Skill stress-tests PRDs, specs, and strategy documents before they face skeptical stakeholders. ## Core Features & Use Cases - Assumption Challenging: Identifies assumptions presented as facts, optimistic timelines, and vague language, then generates critical questions for each. - Failure Scenario Analysis: Maps potential failure modes with likelihood, impact, early warning signs, and mitigation strategies using pre-mortem thinking. - Blind Spot & Consequence Detection: Surfaces unconsidered user segments, technical complexities, operational burdens, and second-order effects. - Use Case: Before presenting a PRD to executives, run it through this Skill to receive a structured challenge document with the hard questions Engineering, Sales, and Legal will ask, plus recommended actions to address top risks. ## Quick Start Ask Claude to run devils-advocate on your PRD to challenge its assumptions and find blind spots before your stakeholder review.

Frequently Asked Questions about devils-advocate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stress test a PRD before stakeholder review?▼

Run the devils-advocate skill on your PRD document. It reviews the full document, challenges key assumptions, generates failure scenarios with likelihood and impact ratings, and produces the hard questions skeptical stakeholders will ask.

What is a pre-mortem analysis for product proposals?▼

Pre-mortem analysis imagines the proposal has already failed and works backward to identify why. This skill applies that technique to surface failure modes, unintended consequences, and second-order effects before execution begins.

Can I use this skill without context files?▼

Yes, it works standalone with generic challenge questions. However, adding context files like company.md, product.md, personas.md, and competitors.md grounds the pushback in your actual constraints, past failures, and competitive landscape.

When should I not use devils advocate on a document?▼

Avoid it during early brainstorming, when a document is already in execution, or for low-stakes decisions. It is designed for high-stakes proposals before stakeholder review, not for ideas still being formed.

How do I adjust the intensity of the challenge?▼

Request lighter output by asking to focus on the top 3 risks only, or request harder scrutiny by asking for maximally skeptical analysis assuming worst case on every assumption. You can also flag specific concerns to challenge deeply.