spike

To validate feasibility before full development, you can run structured throwaway experiments that decompose your idea into independent research questions and document the conclusions. This approach tests concepts and technologies without risking a real build.

A spike experiment in software development is a throwaway prototype used to assess the feasibility of a concept or technology. It involves breaking down an idea into specific questions, researching them, and documenting findings to inform decisions.

You decompose a software concept by identifying the core technical unknowns and breaking them into independent tests. The skill structures this by guiding you through research and build loops for each question to gather evidence.

Yes, throwaway experimentation is designed to test new technologies for existing projects by creating isolated prototypes. This allows you to research and verify integration feasibility before modifying your main codebase.

The best way to document prototype findings is to record your research, implementation steps, and final verdicts in a dedicated directory. This ensures the evidence gathered from your feasibility tests is preserved for decision-making.

You should not use throwaway experiments when a concept is already proven or fully specified. This approach is strictly for assessing unknown feasibility and creating throwaway code, not for building production-ready features.