What problem does it solve? Teams often commit to architectures or libraries before knowing whether they actually work, wasting weeks on dead-end implementations. This Skill structures quick, disposable experiments that answer feasibility questions with evidence before any production code is written. ## Core Features & Use Cases - Structured Spike Decomposition: Breaks an idea into 2-5 independent feasibility questions framed as Given/When/Then statements, ordered by risk so the idea-killing question runs first. - Comparison Spikes: Builds competing approaches side by side (e.g., pdfjs vs camelot for PDF parsing) and produces a head-to-head verdict table with a clear winner. - Evidence-Based Verdicts: Every spike closes with a VALIDATED, PARTIAL, or INVALIDATED verdict documenting what worked, what failed, and recommendations for the real build. - Use Case: Before building a real-time chat feature, spike whether WebSocket streaming delivers LLM tokens to the client in under 100ms, then throw the prototype away and start the real implementation with confidence. ## Quick Start Ask the assistant to spike whether your chosen library or approach actually works for your use case before you commit to building the real feature.
