spike

Run disposable feasibility experiments and produce build or abandon verdicts.

1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/Signmanal/VIGIL --skill spike-signmanal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spike
Source: https://github.com/Signmanal/VIGIL/tree/main/skills/software-development/spike
Command: npx skills add https://github.com/Signmanal/VIGIL --skill spike-signmanal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the waste of committing development resources to unproven ideas by enabling low-cost, disposable experiments to validate feasibility, compare approaches, and surface critical unknowns before full build work begins.

Core Features & Use Cases

  • Feasibility Decomposition: Breaks vague ideas into 2-5 specific, testable questions ordered by risk to target the biggest unknowns first.
  • Comparison Spikes: Supports side-by-side testing of multiple approaches to the same problem with clear head-to-head verdicts.
  • Actionable Verdicts: Produces structured VALIDATED/PARTIAL/INVALIDATED outcomes with concrete recommendations for next steps. Use Case: If you're unsure if a new websocket library can meet sub-100ms latency requirements, you can spike it in an afternoon instead of spending a week building a full feature that might not work.

Quick Start

Use the spike skill to test if the new PDF parsing library can extract structured tables from multi-page documents faster than your current tool.

Frequently Asked Questions about spike

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

FAQPage Schema
What is a throwaway spike for feasibility validation in software development?

A throwaway spike is a low-cost, disposable experiment used for feasibility validation to test unproven technical ideas before committing development resources. It surfaces critical unknowns and produces actionable build or abandon recommendations without permanent code overhead.

How do I compare multiple technical approaches before committing to a full build?

You can use comparison spikes to run side-by-side testing of multiple approaches to the same problem. This delivers clear head-to-head verdicts and structured VALIDATED or INVALIDATED outcomes to recommend next steps without permanent infrastructure overhead.

Can I test if a new library meets specific performance requirements without building a full feature?

Yes, you can spike the new library in an afternoon to test specific constraints like sub-100ms latency or structured table extraction. This disposable proof-of-concept validates MVP feasibility and produces actionable build or abandon recommendations quickly.

When should I avoid using disposable spikes for product planning?

Avoid using disposable spikes when you need permanent code or infrastructure overhead, as they are strictly designed for pre-build validation. Spikes deliver structured verdicts for abandoning or building ideas, not for producing deployable production features.

What outcomes should I expect from running a proof-of-concept experiment for an unproven idea?

Running a proof-of-concept experiment produces structured VALIDATED, PARTIAL, or INVALIDATED verdicts. These actionable outcomes provide concrete recommendations for next steps, ensuring you avoid wasting resources on unproven technical or product ideas.