spike

Builds throwaway prototype experiments to validate technical feasibility before committing to a real build.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/decniner/HermesP1 --skill spike-decniner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spike
Source: https://github.com/decniner/HermesP1/tree/main/.hermes-backup/skills/software-development/spike
Command: npx skills add https://github.com/decniner/HermesP1 --skill spike-decniner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It answers feasibility questions that research alone cannot resolve by building small, disposable prototypes, so you avoid committing to an approach that turns out to be unworkable. ## Core Features & Use Cases - Decompose and Prioritize: Breaks an idea into 2-5 independent feasibility questions framed as Given/When/Then, ordered by risk so the idea-killing question runs first. - Research and Build Loop: Surfaces competing libraries or approaches, picks one, then builds a runnable CLI, HTML page, or small server per spike in a spikes/NNN-name/ directory. - Verdicts and Comparisons: Closes each spike with a VALIDATED, PARTIAL, or INVALIDATED verdict, and produces head-to-head comparisons for parallel approaches (e.g., pdfjs vs camelot). - Use Case: Before building a streaming chat feature, spike whether websocket token streaming reaches the client in under 100ms, then throw the prototype away once the verdict is in. ## Quick Start Spike whether websocket streaming can deliver LLM tokens to the browser in under 100ms before I commit to this architecture.

Frequently Asked Questions about spike

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

FAQPage Schema
How do I validate a technical idea before building it?▼

Run a spike: decompose the idea into 2-5 independent feasibility questions framed as Given/When/Then, order them by risk, then build a small runnable prototype per question. Close each spike with a VALIDATED, PARTIAL, or INVALIDATED verdict and throw the code away.

What is a spike in software development?▼

A spike is a throwaway experiment that answers a specific feasibility question with observable output, such as a runnable CLI or minimal HTML page. It is disposable by design and exists only to de-risk a decision before real implementation begins.

How do I compare two libraries or approaches for a project?▼

Build comparison spikes with a shared number and letter suffixes (e.g., 002a and 002b), one per approach, then write a head-to-head table covering extraction quality, setup complexity, performance, and edge cases. Parallel spikes can be delegated to subagents when both need real engineering.

When should I not use a spike?▼

Skip spiking when the answer is knowable from documentation or reading code, when the work is on the production path and needs a real plan, or when the idea is already validated. Spikes exist only for questions research cannot answer.

What makes a good spike question?▼

A good spike question targets specific feasibility with observable output, such as whether websocket streaming delivers chunks under 100ms. Bad questions are too broad, produce no observable output, or amount to just reading documentation.