spike

Build disposable prototypes to validate uncertain ideas with evidence-backed verdicts.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/MarbleSodas/Mavis --skill spike-marblesodas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spike
Source: https://github.com/MarbleSodas/Mavis/tree/main/skills/software-development/spike
Command: npx skills add https://github.com/MarbleSodas/Mavis --skill spike-marblesodas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you reduce the risk of building the wrong thing by turning uncertain ideas into quick, testable evidence before committing to production work.

Core Features & Use Cases

  • Feasibility spikes: Break an idea into 2–5 feasibility questions and answer each with observable results.
  • Research-then-build loop: Do just enough research to pick an approach, build a minimal prototype, then document a clear verdict.
  • Comparison and iteration: Run parallel variants for head-to-head decisions, then iterate based on what the evidence shows.
  • Decision-ready outputs: Produce a per-spike README with a VALIDATED | PARTIAL | INVALIDATED verdict and a recommendation for the real build.

Quick Start

Use the spike skill to validate an approach by saying: "Spike whether X is feasible for my use case and give me a VALIDATED/PARTIAL/INVALIDATED verdict with evidence."

Frequently Asked Questions about spike

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

FAQPage Schema
How do I validate an idea fast before committing to a full implementation?

Idea validation through throwaway experimentation involves building minimal interactable prototypes to test uncertain approaches and gather evidence. It reduces the risk of building the wrong thing by producing clear VALIDATED or INVALIDATED verdicts before committing to production work.

What is the best way to compare technical approaches during early planning?

The best way to compare technical approaches is running parallel variants for head-to-head decisions. By building minimal prototypes for each approach, you can iterate based on observable evidence and document a clear recommendation for which path to choose for the real build.

How do I run a feasibility spike to test if an approach works for my use case?

Run a feasibility spike by breaking your idea into testable Given/When/Then questions, performing minimal research to pick an approach, and building an interactable prototype. You then document a per-spike README with a VALIDATED, PARTIAL, or INVALIDATED verdict backed by evidence.

Can I use throwaway prototypes for head-to-head comparison of different solutions?

Yes, you can use throwaway prototypes for head-to-head comparison by running parallel variants of your experiment. This allows you to test multiple solutions simultaneously, iterate based on the evidence each prototype produces, and confidently choose the best approach for your production build.

When should I not use feasibility spikes for idea validation?

You should not use feasibility spikes when unknowns can be resolved through documentation review alone. Spikes are designed for early planning scenarios that require hands-on, interactable prototypes to generate observable evidence rather than relying on existing research or theoretical analysis.