What problem does it solve? Backend changes are often accepted based on frontend output or mocks, leaving boundary behavior, failure handling, durable state, and contract compliance unproven. This Skill enforces direct verification of backend behavior before consumer or frontend integration. ## Core Features & Use Cases - Direct Boundary Testing: Exercises the backend through its nearest real boundary such as HTTP handlers, service APIs, commands, workers, queue messages, or webhook receivers. - Failure and State Proof: Validates success paths, important failures, durable state, side effects, rollback, idempotency, and duplicate delivery behavior. - Contract and Dependency Verification: Runs schema-driven contract checks and real-dependency proof against databases, queues, caches, or external services without behavior-erasing mocks. - Use Case: After modifying a payment webhook endpoint, use this Skill to prove the handler processes valid payloads, rejects unauthorized requests, persists state idempotently on duplicate deliveries, and satisfies the canonical API contract. ## Quick Start Verify the backend behavior of my recent changes to the order processing service, including failure cases, durable state, and contract compliance.