vibe-testinglisted

# Vibe Testing ## Overview Vibe testing validates specification documents by simulating real-world scenarios against them using LLM reasoning. Instead of writing code or test harnesses, write **natural-language scenarios** that exercise cross-cutting slices of the spec surface — then trace execution step-by-step, flagging gaps, conflicts, and ambiguities. **Core principle:** If a realistic user scenario cannot be fully traced through the specs, the specs are incomplete. **Best used:** After specs are written, before implementation begins. ## When to Use - Spec docs exist but no implementation yet — validate before building - After major spec changes — regression-test for new gaps - Before implementation planning — find blocking gaps early - Specs span multiple documents — test cross-doc coherence - Designing for multiple deployment contexts — test each context separately **When NOT to use:** - Single-file specs with obvious scope — just review manually - Implementation bugs — use actual tests - API contract validation — use schema validation tools ## Core Method ``` 1. GATHER — Read all spec docs in the target directory 2. SCENARIOS — Write 3-5 vibe test cases (personas + goals + environments) 3. SIMULATE — Trace each scenario step-by-step against the specs 4. CLASSIFY — Tag findings as GAP / CONFLICT / AMBIGUITY 5. SEVERITY — Rate as BLOCKING / DEGRADED / COSMETIC 6. REPORT — Produce gap summary + spec coverage matrix ``` ## Writing a Vibe Test Case Ever