devils-advocate

Extract claims and assumptions from proposals to identify risks and failure evidence.

5|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/yash-gadodia/claude-init --skill devils-advocate-yash-gadodia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devils-advocate
Source: https://github.com/yash-gadodia/claude-init/tree/main/templates/skills/devils-advocate
Command: npx skills add https://github.com/yash-gadodia/claude-init --skill devils-advocate-yash-gadodia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Devil's Advocate skill identifies potential flaws and risks in plans, designs, or PRs, helping to prevent bad decisions from becoming a reality.

Core Features & Use Cases

  • Problem Identification: Challenge plans by searching for flaws, risks, and wrong assumptions.
  • Contextual Analysis: Extract claims, assumptions, and dependencies from proposals.
  • Evidence-based Review: Validate each claim with evidence from the codebase and hypothetical scenarios.
  • Comprehensive Assessment: Stress-test for scalability, failure modes, and long-term viability.

Quick Start

Challenge the design for the new user interface by running: /devils-advocate "user interface design"

Frequently Asked Questions about devils-advocate

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

FAQPage Schema
How do I identify hidden risks and wrong assumptions in my software design proposals?

Risk assessment for design proposals works by extracting claims, identifying assumptions, and searching the codebase for evidence of failure. This review process challenges your plans by validating each claim with evidence and hypothetical scenarios to prevent bad decisions.

Can I use contextual codebase analysis to review a pull request for long-term viability?

Yes, PR review requires a codebase and context to evaluate the proposal within. It analyzes extracted dependencies and assumptions to stress-test the pull request for scalability, failure modes, and long-term viability using evidence from the existing code.

What is the best way to stress-test a project plan for potential failure modes?

The best way to stress-test project safety is by using evidence-based review to validate claims with hypothetical scenarios. This comprehensive assessment searches for problem identification by challenging the plan's assumptions against the actual codebase environment.

Does plan validation work without an existing codebase to evaluate the context?

No, plan validation requires a codebase and context to evaluate the proposal within. The review process depends on extracting dependencies and searching for evidence of failure or risk from the actual code to effectively challenge the claims made.