Skip to content
Development
Skill

/gsd-spike

Spike an idea through experiential exploration, or propose what to spike next (frontier mode)

From plugin
gsd-core
8k71 skills34 agents71 commands7 hooks
Install
$ npx -y skills add open-gsd/gsd-core --skill gsd-spike --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/gsd-spike

Context preview

The summary Claude sees to decide when to auto-load this skill.

Spike an idea through experiential exploration, or propose what to spike next (frontier mode)

SKILL.md

gsd-spike.SKILL.md
name: gsd-spike
description: "Spike an idea through experiential exploration, or propose what to spike next (frontier mode)"
argument-hint: "[idea to validate] [--quick] [--text] [--wrap-up] or [frontier]"
allowed-tools:
  - Read
  - Write
  - Edit
  - Bash
  - Grep
  - Glob
  - AskUserQuestion
  - WebSearch
  - WebFetch
  - mcp__context7__resolve-library-id
  - mcp__context7__query-docs

<objective> Spike an idea through experiential exploration — build focused experiments to feel the pieces of a future app, validate feasibility, and produce verified knowledge for the real build. Spikes live in `.planning/spikes/` and integrate with GSD commit patterns, state tracking, and handoff workflows.

Two modes:

  • **Idea mode** (default) — describe an idea to spike
  • **Frontier mode** (no argument or "frontier") — analyzes existing spike landscape and proposes integration and frontier spikes

Does not require prior new-project setup — auto-creates `.planning/spikes/` if needed. </objective>

<execution_context> @~/.claude/gsd-core/workflows/spike.md @~/.claude/gsd-core/workflows/spike-wrap-up.md @~/.claude/gsd-core/references/ui-brand.md </execution_context>

<runtime_note> **Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`. </runtime_note>

<context> Idea: $ARGUMENTS

**Available flags:**

  • `--quick` — Skip decomposition/alignment, jump straight to building. Use when you already know what to spike.
  • `--text` — Use plain-text numbered lists instead of AskUserQuestion (for non-Claude runtimes).
  • `--wrap-up` — Package spike findings into a persistent project skill for future build conversations. Runs the spike-wrap-up workflow.

</context>

<process> Parse the first token of $ARGUMENTS:

  • If it is `--wrap-up`: strip the flag, execute the spike-wrap-up workflow
  • Otherwise: pass all of $ARGUMENTS as the idea to the spike workflow end-to-end.

Preserve all workflow gates (prior spike check, decomposition, research, risk ordering, observability assessment, verification, MANIFEST updates, commit patterns). </process>

Read more
Ships withgsd-core

Git. Ship. Done. A light-weight meta-prompting, context engineering, and spec-driven development system for Claude Code, OpenCode, Antigravity CLI, Kimi CLI, Kilo, Codex, Copilot, Cursor, Windsurf, and more.

Get the whole plugin