vibe-testing

What problem does it solve?

Specification gaps, conflicts, and ambiguities are often only discovered late in the development process during implementation, leading to costly rewrites, delayed launches, and wasted engineering effort. This skill enables you to identify these issues early using LLM reasoning, before any code is written, reducing risk and rework.

Core Features & Use Cases

• Scenario-based spec validation: Simulate real-world user journeys against your specification documents to trace cross-cutting requirements and surface missing definitions.
• Structured gap reporting: Classify findings by severity (BLOCKING, DEGRADED, COSMETIC) to prioritize fixes, and generate spec coverage matrices to identify untested documentation.
• Use case: Before starting build work on a new e-commerce checkout flow, run vibe tests to catch gaps like mismatched payment retry timing and inventory hold durations that would otherwise cause mid-implementation surprises.

Quick Start

Ask your AI coding agent to run a vibe test on your project's specification documents to identify gaps and ambiguities before you begin writing implementation code.