spike

Decompose an idea into feasibility questions and guide a lightweight build to a verdict.

2|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/john-data-chen/hermes-agent-backup --skill spike-john-data-chen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spike
Source: https://github.com/john-data-chen/hermes-agent-backup/tree/main/skills/software-development/spike
Command: npx skills add https://github.com/john-data-chen/hermes-agent-backup --skill spike-john-data-chen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Throwaway experiments to validate an idea before building, helping teams quickly evaluate feasibility and surface unknowns without committing to production work.

Core Features & Use Cases

  • Decompose a concept into 2-5 independent feasibility questions, each framed as Given/When/Then.
  • Align, research, build, and verdict loops to iteratively refine findings.
  • Support spike types (standard and comparison) and lightweight, disposable outputs when decisions are not yet clear.
  • Optional extended workflow integration with the GSD system if installed; otherwise use the lightweight spike.

Quick Start

Decompose your idea into 2–5 spike questions, run focused research and a lightweight build, and capture 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 run a feasibility spike to validate an idea before building?

To run a feasibility spike, decompose your idea into 2-5 independent feasibility questions framed as Given/When/Then, then execute align, research, build, and verdict loops to iteratively refine findings and capture a final decision.

What are the limitations of using throwaway experiments for idea validation?

Yes, the comparison spike type supports side-by-side comparisons of approaches. It guides a lightweight, disposable build to validate or invalidate assumptions, helping teams evaluate multiple technical directions before selecting one for production.

Do I need the GSD system installed to use this spike workflow?

Throwaway experiments produce disposable outputs intended for decision-making, not production deployment. They are limited to surfacing unknowns and validating assumptions, meaning the lightweight build artifacts should not be carried directly into your final production codebase.

Do I need the GSD system installed to use this spike workflow?

No, you do not need the GSD system installed. The spike workflow operates as a lightweight, standalone process for idea validation, but optionally supports extended workflow integration with the GSD system if it is already installed in your environment.