What problem does it solve? Teams often commit to architectures or libraries before knowing whether they actually work. This Skill structures quick, disposable experiments that answer feasibility questions with real evidence instead of assumptions. ## Core Features & Use Cases - Structured Spike Loop: Decompose an idea into 2-5 feasibility questions, research approaches, build minimal prototypes, and record a VALIDATED / PARTIAL / INVALIDATED verdict per spike. - Comparison Spikes: Run competing approaches (e.g., pdfjs vs camelot) side by side and produce a head-to-head comparison table with a clear winner recommendation. - Frontier Mode: Analyze existing spikes to surface integration risks, unproven data handoffs, and gaps worth spiking next. - 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 Ask the agent to spike whether your chosen library or approach actually works for your use case before you commit to the full implementation.