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 evidence instead of assumptions. ## Core Features & Use Cases - Spike Decomposition: Breaks an idea into 2-5 independent feasibility questions framed as Given/When/Then statements, ordered by risk. - Comparison Spikes: Builds parallel variants (e.g., pdfjs vs camelot) and produces a head-to-head comparison table with a declared winner. - Structured Verdicts: Each 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 under 100ms, then throw the prototype away once the question is answered. ## 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.
