spike

You validate technical feasibility by running low-cost, disposable experiments that test specific implementation approaches before committing resources. This skill decomposes complex ideas into testable questions, builds minimal prototypes, and documents findings with a clear verdict.

Comparing technical approaches is best done through side-by-side prototype testing. This skill builds multiple minimal versions of a prototype to evaluate different tools or methodologies, documenting the distinct findings for each approach to help you choose.

You mitigate high-risk technical unknowns early by isolating them into testable questions and running rapid experiments. This skill creates standalone spike directories to investigate uncertainties, preventing wasted effort on unviable solutions.

Yes, terminal access and file system capabilities are required. This skill manages isolated, standalone spike directories to conduct rapid technical experiments, which necessitates direct interaction with the local file system environment.

To run a quick MVP experiment for a websocket-based implementation, you define the feasibility question and let the skill build a minimal prototype. It conducts the rapid experiment in an isolated directory and returns a documented finding with a clear verdict.

You should avoid throwaway prototypes when uncertainty is low or the technical approach is already proven. This experimentation method is designed specifically to solve uncertainty and validate project feasibility before a full production build, making it redundant for known solutions.