critic-edge-cases

Detect missing edge cases in Failsafe contracts and output JSON findings.

3|Updated May 20, 2026
One-click install
npx skills add https://github.com/iampawan/Manifest --skill critic-edge-cases
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: critic-edge-cases
Source: https://github.com/iampawan/Manifest/tree/main/skills/critic-edge-cases
Command: npx skills add https://github.com/iampawan/Manifest --skill critic-edge-cases

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill uncovers missing edge cases, ambiguous scenarios, and unspecified failure modes in Failsafe contracts, enhancing the contract verification process.

Core Features & Use Cases

  • Edge Case Detection: Scans contracts for overlooked edge cases and ambiguous scenarios.
  • Automated Findings: Provides a JSON array of findings with severity and suggestions.
  • Use Case: Ensure that a software specification is robust by automatically detecting potential gaps in its behavior and state transitions.

Quick Start

Run the critic-edge-cases skill on your Failsafe contract to automatically identify any missing edge cases.

Frequently Asked Questions about critic-edge-cases

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

FAQPage Schema
How do I detect missing edge cases in Failsafe contracts?

Edge case detection in Failsafe contracts involves scanning software specifications for ambiguous scenarios and unspecified failure modes. The process outputs a JSON array of findings detailing severity levels and actionable suggestions for improvement.

What is edge case detection for software specifications?

Edge case detection identifies overlooked conditions and ambiguous state transitions within a software specification. It ensures behavioral robustness by automatically uncovering potential gaps in failure modes before contract verification.

How do I automate finding unspecified failure modes in software contracts?

Automating unspecified failure mode detection involves running a critic skill on the Failsafe contract. It operates within the contract-verify orchestrator to output findings as a structured JSON array with severity and improvement suggestions.

Does edge case detection require a specific contract-verify orchestrator?

Yes, this edge case detection operates within the contract-verify orchestrator. It processes Failsafe contracts directly to identify gaps in behavior and state transitions without requiring external dependencies.

How do I report ambiguous scenarios in Failsafe contract verification?

Ambiguous scenarios in Failsafe contract verification are reported as a JSON array. Each finding includes a severity level and specific suggestions for improving the software specification's robustness.