edge-case-analyst

Identify potential failure scenarios for planned features during design.

6|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/dangeles/claude --skill edge-case-analyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edge-case-analyst
Source: https://github.com/dangeles/claude/tree/main/claude-config/skills/edge-case-analyst
Command: npx skills add https://github.com/dangeles/claude --skill edge-case-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams and engineers identify potential failure scenarios early in the design process, reducing the risk of costly changes after implementation.

Core Features & Use Cases

  • Phase-driven risk discovery: Systematically identifies risks across user behavior, system states, tools, data, concurrency, and integration points.
  • Taxonomy-based analysis: Applies a structured taxonomy (User Behavior, System, Tool, Data, Concurrency, Integration) to categorize risks.
  • Actionable mitigation guidance: Provides recommended strategies such as pre-flight checks, graceful degradation, retries with backoff, user prompts, and rollback plans.
  • Structured reporting: Generates concise risk summaries and prioritized action items for design reviews.

Quick Start

Run the edge-case-analyst during planning sessions to enumerate potential risks for a feature and generate a prioritized mitigation plan. Example: open a planning doc and execute the risk discovery prompts to capture edge-case scenarios.

Frequently Asked Questions about edge-case-analyst

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

FAQPage Schema
How do I identify edge-case risks before feature implementation?

Edge-case risk identification applies a taxonomy across user behavior, system states, tools, data, concurrency, and integration points. This Skill executes a phase-driven workflow to surface failure scenarios and generate prioritized mitigation strategies during design reviews.

What is FMEA and when should I use it for design review?

FMEA, or Failure Mode and Effects Analysis, is a structured method for evaluating potential failures across system components. You can trigger an optional Full Mode FMEA during the risk assessment phase to deeply analyze failure modes and their effects on planned features.

How do I create a risk matrix for software feature planning?

Creating a risk matrix involves categorizing potential failure scenarios by taxonomy and assessing their impact. This Skill generates structured reports with prioritized action items, applying mitigation strategies like pre-flight checks, graceful degradation, and rollback plans for design reviews.

Can I run pre-implementation risk analysis without external dependencies?

Pre-implementation risk analysis runs without external dependencies. The Skill operates standalone during planning sessions, using your feature documentation as context to enumerate potential edge-case scenarios and generate structured mitigation guidance.

What mitigation strategies are recommended for concurrency and integration risks?

Recommended mitigation strategies for concurrency and integration risks include retries with backoff, pre-flight checks, and graceful degradation. The Skill provides actionable guidance tailored to the specific failure scenarios surfaced during the taxonomy-based analysis.

Does this approach work for analyzing data quality and user behavior edge cases?

Yes, this approach works for analyzing data quality and user behavior edge cases. The Skill explicitly applies a structured taxonomy that includes User Behavior, Data, System, Tool, Concurrency, and Integration categories to ensure comprehensive risk discovery.