What problem does it solve? Teams often commit to specs and implementations before knowing whether an approach is technically feasible, wasting effort on dead ends. This Skill structures short, time-boxed spikes that answer one specific question with measurable evidence before any production code is written. ## Core Features & Use Cases - Spike Framing: Forces a one-sentence question, explicit time box, and success criteria before any code is written. - Throwaway Code Discipline: Defines branch naming, salvage rules, and deletion defaults so prototype code never silently becomes production code. - Structured Findings Report: Produces a verdict (proceed, pivot, blocked) with measured results, risks, and recommended next steps. - Use Case: Before committing to a CSV import feature, run a 3-hour spike to verify whether streaming parses 50k rows under 2 seconds, then hand the findings to the spec-writing workflow. ## Quick Start Ask the agent to run a time-boxed spike answering whether your chosen library or approach meets a specific measurable constraint, and produce a findings report.
