spike

Name: spike
Availability: InStock
Author: jleechanorg

Decompose ideas into feasibility questions and generate verdicts for testing prototypes.

Updated Jun 28, 2026

Search Tags:#workflow #feasibility #prototype #spike #learning-loop #rapid-validation

Ready to run

npx skills add https://github.com/jleechanorg/hermes-agent --skill spike-jleechanorg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spike
Source: https://github.com/jleechanorg/hermes-agent/tree/main/skills/software-development/spike
Command: npx skills add https://github.com/jleechanorg/hermes-agent --skill spike-jleechanorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams and engineers explore ideas quickly by turning vague concepts into testable spikes, reducing wasted effort on unviable concepts.

Core Features & Use Cases

Decompose an idea into 2-5 feasibility questions and generate observable outputs.
Run lightweight prototypes and gather verdicts to guide decision making.
Create repeatable workflows for early-stage exploration and risk assessment.

Quick Start

Create a spike by decomposing the idea into 2-5 feasibility questions, prototype observable outputs for each, and record a final verdict.

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 a new product idea quickly?▼

Validate feasibility by isolating ideas into disposable spikes that decompose concepts into 2-5 questions and generate observable outputs. This repeatable workflow builds lightweight prototypes to gather verdicts and guide decision making for early product exploration.

What is a spike in software architecture tradeoff analysis?▼

A spike is a throwaway experiment for rapid validation of technical risks during architecture tradeoff analysis. It requires a standalone directory to research and build lightweight implementations, ending with a finished README and verdict section to guide decisions.

How do I structure a rapid validation prototype for early stage exploration?▼

Structure rapid validation prototypes by creating a standalone directory per spike. Follow a repeatable workflow to decompose, align, research, build, and evaluate the prototype, ensuring outputs include a finished README with a clear verdict section for decision making.

Can I use this spike workflow for risk assessment across research tasks?▼

Yes, the spike workflow applies to risk assessment across research tasks and lightweight implementations. It isolates unknowns into disposable experiments, generating observable outputs and a final verdict to evaluate technical or product viability before full commitment.

What is the best way to document the results of a throwaway experiment?▼

The best way to document throwaway experiments is to output a finished README with a dedicated Verdict section. This captures the rapid validation results and observable outputs from the spike, creating a repeatable record for early product exploration and risk assessment.

When should I not use a spike for prototype testing?▼

Avoid using a spike for prototype testing when the concept is already well-understood or requires production-ready implementation. Spikes are designed for rapid validation and early-stage exploration, not for building scalable architecture or final deliverables.