spike

Decompose ideas into feasibility questions and test them with disposable prototypes.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/srivtx/supercharger-opencode --skill spike-srivtx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spike
Source: https://github.com/srivtx/supercharger-opencode/tree/main/engineering/spike
Command: npx skills add https://github.com/srivtx/supercharger-opencode --skill spike-srivtx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The spike skill helps validate ideas by creating disposable experiments, allowing users to test feasibility and compare approaches before committing to a full build.

Core Features & Use Cases

  • Throwaway Experiments: Design and run experiments to validate an idea before building.
  • Decomposition and Research: Break down ideas into feasibility questions and research possible approaches.
  • Building and Verdict: Develop quick prototypes and provide a clear verdict on the results.
  • Integration Risks and Data Handoffs: Identify potential integration risks and data handoffs between different spikes.

Quick Start

To begin a spike, execute the command: spike new "Experiment Name" --description "Experiment Description".

Frequently Asked Questions about spike

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate the feasibility of an idea before full-scale implementation?

You can validate feasibility by running disposable experiments to test approaches before committing to a full build. This process decomposes ideas into feasibility questions, researches potential solutions, and builds quick prototypes to provide a clear verdict on the results.

What is a throwaway experiment in software prototyping?

A throwaway experiment is a disposable prototype designed to test an idea's feasibility and compare approaches. It allows you to research solutions, validate potential integration risks, and provide verdicts on results before committing to full-scale implementation.

How do I start a new feasibility experiment for idea validation?

To start a feasibility experiment, execute the command `spike new "Experiment Name" --description "Experiment Description"`. This initiates the process of breaking down your idea into research questions and building quick prototypes.

Can I identify integration risks and data handoffs between different experiments?

Yes, the experimentation process explicitly identifies potential integration risks and data handoffs between different disposable prototypes. This ensures you understand feasibility constraints and dependencies before proceeding with full-scale implementation.

What is the best way to compare approaches for building a new feature?

The best way to compare approaches is by building quick prototypes as disposable experiments. This method researches possible solutions, tests feasibility, and provides a clear verdict on the results, allowing you to validate approaches before full implementation.

When should I not use throwaway experiments for prototyping?

You should not use throwaway experiments when you need production-ready code, as these are disposable prototypes designed only for idea validation. They are strictly for testing feasibility and providing verdicts before committing to a full-scale build.