skeptic

Identify edge cases, operational costs, and logic weaknesses in product ideas.

Updated Aug 23, 2026

Search Tags:#edge-cases #product-design #risk-analysis #failure-modes #skeptic #disaster-scenarios

Ready to run

npx skills add https://github.com/ericklemos/ai-tools --skill skeptic-ericklemos

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skeptic
Source: https://github.com/ericklemos/ai-tools/tree/main/.agents/skills/skeptic
Command: npx skills add https://github.com/ericklemos/ai-tools --skill skeptic-ericklemos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exposes edge cases, operational costs, and logic weaknesses to protect users by imagining every way the system can break. The team's internal red team, guarding against failures before they happen.

Core Features & Use Cases

Systematically interrogates designs to uncover edge cases and hidden costs.
Documents risk scenarios, mitigation steps, and decision rationale for stakeholders.
Supports cross-team memory and disaster-scenario tracking for ongoing risk management.

Quick Start

Identify a proposed feature and list the top three failure modes with mitigation steps.

Frequently Asked Questions about skeptic

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

FAQPage Schema

How do I identify edge cases and failure modes in a product design before shipping?▼

To identify edge cases and failure modes in product design, systematically interrogate the proposed feature to uncover hidden operational costs and logic weaknesses. This involves rigorous scenario planning and worst-case analyses to expose disaster scenarios before they impact users.

What is risk analysis for disaster scenarios and when do I need it for feature proposals?▼

Risk analysis for disaster scenarios systematically exposes how a system can break under stress. You need it for feature proposals, architectural designs, and operational workflows to surface failure modes, cost drivers, and data risks prior to launch.

How do I document operational costs and data risks for stakeholder review?▼

To document operational costs and data risks for stakeholders, list the top failure modes with specific mitigation steps. Capture the decision rationale to support cross-team memory and enable ongoing disaster-scenario tracking for risk management.

Can I use worst-case analysis to find logic weaknesses in architectural designs?▼

Yes, you can apply worst-case analysis to architectural designs to surface logic weaknesses and cost drivers. It interrogates the architecture to expose hidden operational costs and failure modes, requiring rigorous scenario planning to protect against system failures.

What's the best way to surface hidden cost drivers in operational workflows?▼

The best way to surface hidden cost drivers in operational workflows is to systematically interrogate them using scenario planning. This process exposes edge cases, data risks, and logic weaknesses, documenting disaster scenarios for stakeholder review and ongoing risk management.