spike

Runs falsifiable experiments to decide whether an idea warrants a project.

1|1|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/nearmap/shipyard --skill spike-nearmap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spike
Source: https://github.com/nearmap/shipyard/tree/main/skills/spike
Command: npx skills add https://github.com/nearmap/shipyard --skill spike-nearmap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deciding whether an idea deserves engineering investment often relies on intuition rather than evidence. This Skill structures exploratory spikes: it reproduces current production behaviour as a validated baseline, designs a falsifiable experiment, measures both gain and regression, and records a directional verdict with inspectable evidence. ## Core Features & Use Cases - Baseline Reproduction: Locates real production behaviour and representative data, then validates reproduction fidelity against known examples before comparing alternatives. - Falsifiable Experiment Design: Defines success bars, primary and regression metrics, representative and adversarial slices, and controls for leakage or confounding. - Evidence-Backed Verdicts: Produces a standalone reproducible artifact folder with figures, tables, and numeric evidence, pressure-tests conclusions through adversarial debate, and posts a tracker verdict comment. - Use Case: A team suspects a new ranking algorithm could outperform the current one. Run a spike to reproduce the production baseline offline, measure improvement and regression on representative and adversarial slices, and receive a stop/iterate/plan verdict plus a /sy:plan-ready brief if the idea clears the bar. ## Quick Start Ask the AI to run a spike on your idea, providing the problem statement, the success bar, and the data anchors it should use as ground truth.

Frequently Asked Questions about spike

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

FAQPage Schema
How do I run an exploratory spike before starting a project?▼

Provide the problem, a falsifiable success bar, and data anchors. The spike reproduces current production behaviour as a baseline, designs an experiment with gain and regression metrics, and returns a directional verdict with a reproducible evidence artifact.

What makes a spike experiment falsifiable?▼

A falsifiable experiment defines an explicit success bar, a comparison baseline, primary metrics, and regression metrics in the opposite direction. It also includes representative and adversarial data slices plus controls for leakage or confounding where relevant.

What happens if the problem does not reproduce during a spike?▼

A failed reproduction is not treated as a negative result immediately. The spike first verifies the premise, data selection, baseline fidelity, ordering assumptions, and sampling bias; if it still does not reproduce, that is reported plainly without manufacturing a positive result.

Does the spike produce production-ready code?▼

No. The spike produces a standalone reproducible artifact folder with run instructions, baseline reproduction, alternative implementation, metrics, evidence, and limitations. If the idea clears the bar, it outputs a brief for starting a proper planning phase instead.

When should I not use an exploratory spike?▼

Avoid a spike when the task is a well-understood, PR-sized change with no open question about feasibility or value. Spikes are for directional decisions under uncertainty, not for routine implementation work.