spike

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

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/i-bebsi/hermes-agent --skill spike-i-bebsi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spike
Source: https://github.com/i-bebsi/hermes-agent/tree/main/hermes-config/skills/software-development/spike
Command: npx skills add https://github.com/i-bebsi/hermes-agent --skill spike-i-bebsi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It answers feasibility questions about an idea before you invest in production code, by building small disposable prototypes that produce observable evidence instead of assumptions. ## Core Features & Use Cases - Decompose ideas into spikes: Breaks a vague idea into 2-5 independent feasibility questions framed as Given/When/Then statements, ordered by risk. - Research then build: Surveys competing libraries and approaches, picks one, and builds a runnable CLI, HTML page, or small server per spike in a spikes/ directory. - Comparison spikes and verdicts: Runs parallel head-to-head variants (e.g., pdfjs vs camelot) and closes each spike with a VALIDATED, PARTIAL, or INVALIDATED verdict plus a recommendation for the real build. - Use Case: Before committing to a websocket-based streaming architecture, spike whether LLM token chunks reach the client under 100ms, then throw the code away once the verdict is in. ## Quick Start Ask the agent to spike whether your idea is feasible, for example: "Spike whether I can stream LLM tokens over websockets to the browser with low latency."

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, build a small throwaway prototype for the riskiest question first, and record a verdict with evidence. Discard the code once the question is answered.

What is a spike in software development?▼

A spike is a disposable experiment that answers a specific feasibility question with observable output, such as a runnable CLI or minimal web page. It is not production code and is thrown away after producing a VALIDATED, PARTIAL, or INVALIDATED verdict.

How do I compare two libraries for the same task?▼

Build comparison spikes: give both variants a shared number with letter suffixes (002a, 002b), implement each approach back to back or in parallel, then write a head-to-head table covering quality, setup complexity, and performance to pick a winner.

When should I not use a spike?▼

Skip spiking when the answer is knowable from documentation or reading existing code, when the work is on the production path (use a planning workflow instead), or when the idea is already validated and you can go straight to implementation.

What makes a good spike question?▼

A good spike question targets specific feasibility with observable output, such as whether streamed tokens arrive under 100ms. Bad questions are too broad, produce no observable result, or merely ask to read documentation about a topic.