spike

A spike is a throwaway experiment used to validate the feasibility of a new software feature before committing to a full build. You should use spikes during ideation to reduce risk and wasted effort on unproven ideas.

Validate technical feasibility by decomposing your idea into 2-5 independent, disposable spikes. Build these minimal experiments in parallel or sequence to test core assumptions, then capture a formal verdict to guide your next steps.

Yes, you can align multiple prototype spikes for parallel exploration. This rapid iteration approach allows you to test different feasibility questions simultaneously, enabling faster decision gating before starting the actual build.

Structure throwaway experiments by creating a minimal spike directory with a lightweight artifact structure. Each spike should contain a runnable entry point that directly demonstrates and answers your core feasibility question.

Capture learnings by producing a formal verdict at the end of your spike workflow. This verdict documents the outcomes of your disposable experiments, ensuring the results effectively guide the architecture of the real build.

Avoid using spikes for feature ideation when the implementation path is already well-understood and low-risk. Spikes are designed for exploring unknown technical feasibility, so they add unnecessary overhead if no validation is required.