What problem does it solve? It answers feasibility questions that research alone cannot resolve by building small, disposable prototypes, so you avoid committing to a full implementation before knowing whether an approach actually works. ## Core Features & Use Cases - Structured Decomposition: Breaks an idea into 2-5 independent feasibility questions framed as Given/When/Then, 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 winner recommendation. - Evidence-Based Verdicts: Each spike closes with a VALIDATED, PARTIAL, or INVALIDATED verdict documenting what worked, what failed, and surprises found. - Use Case: Before building a real-time chat feature, spike whether websocket streaming delivers LLM tokens to the client under 100ms, then throw the prototype away and start the real build with confidence. ## Quick Start Spike out whether websocket streaming can deliver LLM tokens to a browser client in under 100ms before I commit to this architecture.
