Checker

Detect edge cases and challenge assumptions through three verification questions.

83|71|Updated Jul 7, 2025
One-click install
npx skills add https://github.com/nikhilvallishayee/universal-pattern-space --skill checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Checker
Source: https://github.com/nikhilvallishayee/universal-pattern-space/tree/main/.claude/skills/pattern-space/perspectives/checker
Command: npx skills add https://github.com/nikhilvallishayee/universal-pattern-space --skill checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides rigorous validation and reality-testing, helping users find edge cases, test assumptions, and catch fatal flaws before they become expensive. It acts as constructive skepticism, strengthening ideas through adversarial testing.

Core Features & Use Cases

  • Three Core Questions: Systematically asks "What could go wrong?", "What are we assuming?", and "How do we verify?" to expose vulnerabilities.
  • Edge Case Detection: Probes for negative, zero, infinite, or simultaneous conditions to ensure robustness.
  • Assumption Exposure: Uncovers hidden assumptions that often lead to unexpected failures.
  • Use Case: Before launching a new product feature, this skill can rigorously test the "happy path" assumptions by asking about edge cases (e.g., what if input is negative, zero, or text instead of numbers?), preventing costly post-launch bugs.

Quick Start

When needing to find edge cases or test assumptions, activate Checker. Example: User: "This handles everything" Checker: "What if negative? Zero? Infinite? Text not numbers? Simultaneous users?" User: "I tested NONE of that" Checker: "I know. Fix those, THEN trust it" Speak AS Checker: "What if..." not "Checker warns..."

Frequently Asked Questions about Checker

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

FAQPage Schema
How do I find edge cases and flawed assumptions before launch?

Edge case detection systematically exposes vulnerabilities by asking what could go wrong, what assumptions underlie your plan, and how you'll verify them. This catches negative values, zero inputs, infinite conditions, and concurrent scenarios that typical testing misses, preventing costly post-launch failures.

What's the best way to validate assumptions during planning and design reviews?

Validation through adversarial testing surfaces hidden assumptions by forcing you to articulate them explicitly, then challenges each one with evidence requirements. This strengthens ideas and decisions by exposing gaps before they become expensive problems in code or production.

When should I apply critical thinking and reality testing to catch flaws?

Apply rigorous validation during planning, design reviews, code reviews, risk assessments, and decision-making—any stage where untested assumptions could cascade into failures. Early questioning prevents rework and reduces the cost of discovering problems later.

How do I test assumptions in code and product features systematically?

Systematic testing asks three core questions: what could go wrong, what are we assuming, and how do we verify it works. This uncovers robustness gaps like missing input validation, boundary conditions, and race conditions that manual testing often overlooks.

Can I use adversarial testing to improve risk management and decision quality?

Yes. Adversarial testing strengthens risk management by forcing explicit articulation and proof of assumptions before proceeding. This constructive skepticism reduces blind spots in strategy, planning, and critical decisions across product, engineering, and business contexts.