spike

Determine PROCEED, REDESIGN, or DEFER for unresolved pipeline questions via timeboxed investigation.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/heymishy/2x2-v3-28-03-20216 --skill spike-heymishy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spike
Source: https://github.com/heymishy/2x2-v3-28-03-20216/tree/main/.github/skills/spike
Command: npx skills add https://github.com/heymishy/2x2-v3-28-03-20216 --skill spike-heymishy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spike handles unknowns that block pipeline progress by providing a structured outcome artefact — PROCEED, REDESIGN, or DEFER — that feeds back into decisions and unblocks delivery.

Core Features & Use Cases

  • Time-boxed investigation prompts a concrete question, scope, and done condition before any work begins.
  • Produces a clear, actionable outcome that informs the next pipeline step and reduces rework.
  • Supports collaboration with defined discovery handoff and decisions logging.

Quick Start

Answer a concrete spike question within a timeboxed scope and define the done condition to determine PROCEED, REDESIGN, or DEFER.

Frequently Asked Questions about spike

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

FAQPage Schema
How do I resolve unknowns blocking my engineering pipeline progress?

To resolve unknowns blocking pipeline progress, run a timeboxed spike that requires a concrete investigation question, a scoped done condition, and explicit outcome options to guide subsequent decisions.

What is a spike investigation in product and engineering pipelines?

A spike investigation is a timeboxed research method that resolves genuine unknowns by prompting a concrete question, defined scope, and done condition to determine whether to proceed, redesign, or defer.

How do I structure a timeboxed investigation to unblock delivery decisions?

Structure a timeboxed investigation by defining a concrete spike question, setting a scoped done condition, and selecting from explicit outcome options to produce a clear, actionable artefact that unblocks delivery.

When should I defer, redesign, or proceed after a spike outcome?

You defer, redesign, or proceed after a spike outcome based on whether the timeboxed investigation resolved the unknowns sufficiently to continue current plans, require a new approach, or postpone the work.

Do I need a defined done condition before starting a spike?

Yes, you need a defined done condition before starting a spike because the timeboxed investigation requires a clearly scoped question and explicit outcome options to produce a decisive and actionable result.

Why does my pipeline review encounter unknowns that cause rework?

Pipeline reviews encounter unknowns that cause rework when investigations lack a structured outcome artefact, making it necessary to apply timeboxed spikes with concrete questions and explicit decisions to reduce subsequent rework.