spike

Decomposes ideas into testable feasibility questions and produces a verdict.

3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill spike-vtgiang-dotcom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spike
Source: https://github.com/vtgiang-dotcom/Solo-Code-Harness/tree/main/.gemini/antigravity/skills/spike
Command: npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill spike-vtgiang-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spikes provide a lightweight, disposable way to validate an idea before committing to a full build, helping you uncover feasibility, risks, and alternative approaches without impacting production.

Core Features & Use Cases

  • Decompose ideas into 2-5 independent feasibility questions per spike.
  • Align and decide on build priorities by evaluating multiple approaches side by side.
  • Produce a verdict for the real build to guide future development or discard the idea.

Quick Start

Provide a concise idea and ask me to run a spike to test its feasibility.

Frequently Asked Questions about spike

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

FAQPage Schema
What is a spike in software development and when should I use it?

A spike is a lightweight, disposable prototype used to validate feasibility and surface unknowns before committing to a full build. Use it during early-stage concepts to test ideas quickly without impacting production environments.

How do I test the feasibility of an idea before building it?

Test idea feasibility by decomposing the concept into 2-5 independent questions and running a disposable spike. This deterministic workflow produces reviewable outputs, allows resets, and yields a clear verdict for future integration.

What's the best way to compare multiple technical approaches for a prototype?

Comparing technical approaches is best handled by running side-by-side spikes to evaluate feasibility. This process aligns build priorities and produces a decisive verdict on which approach to guide future development or discard.

Can I use a spike workflow for early-stage concept validation across different domains?

Yes, you can apply spike workflows to early-stage concepts across various domains to surface unknowns. The process decomposes ideas into independent feasibility questions, enforcing a deterministic workflow with reviewable outputs and clear verdicts.

What are the limitations of using disposable spikes for project planning?

Disposable spikes are limited to early-stage idea validation and feasibility testing, not full production builds. They are designed to be thrown away after producing a verdict, ensuring no direct impact on your production environment.