> ## Documentation Index
> Fetch the complete documentation index at: https://gump.build/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Spike

> Technical exploration and analysis. Produces a document, not code.

# Spike

Technical exploration. Analysis, not code.

<Note>
  **Community pattern** — copy this YAML and customize the prompt. Not available as a built-in via `gump run`.
</Note>

## When to use

When you need a technical analysis, not an implementation. Architecture decisions, feasibility studies, trade-off analyses.

## The workflow

```yaml theme={null}
name: spike
max_budget: 3.00

steps:
  - name: research
    type: validate
    get:
      context:
        - file: "docs/architecture.md"
        - bash: "find . -name '*.go' | head -30"
      prompt: |
        Analyze: {spec}
        Produce a detailed technical analysis with recommendations.
        Consider trade-offs, risks, and alternatives.
    run:
      agent: claude-opus
    gate: []
```

## How it works

A single step with `type: validate` and no gate. The agent explores the question using the codebase and architecture docs as context. Its output is in the state — inspect with `gump report`.

No code changes, no git diff. The worktree is read-only.

## Customize

<AccordionGroup>
  <Accordion title="Add web research">
    When `search` and `surf` types ship (day 2), chain a research step before the analysis.
  </Accordion>

  <Accordion title="Multiple perspectives">
    Add a parallel group with different agents analyzing the same question, then an arbiter.
  </Accordion>
</AccordionGroup>