What problem does it solve? Committing to an implementation based on untested assumptions leads to costly rework. This Skill de-risks ideas by running focused, time-boxed experiments that produce concrete evidence before you build. ## Core Features & Use Cases - Assumption Identification: Generates and ranks 3-7 high-risk assumptions (integration, performance, compatibility, correctness, feasibility) for user confirmation. - Isolated Spike Execution: Runs all exploratory code inside a gitignored .tmp/ directory, using parallel sub-agents to validate independent assumptions concurrently. - Evidence-Based Reporting: Writes a SPIKE-REPORT.md with a go/no-go verdict, per-assumption results with confidence levels, surprises, risks, and reproduction steps. - Use Case: Before building a feature on a new library, spike whether the library supports your use case, whether performance holds at expected scale, and whether edge cases are handled — then decide with evidence. ## Quick Start Ask the agent to run a tech spike on your idea, for example: "Spike whether we can stream large files through this API without hitting memory limits."