Files
get-shit-done/commands/gsd/spike.md
Tom Boucher b1a670e662 fix(#2697): replace retired /gsd: prefix with /gsd- in all user-facing text (#2699)
All workflow, command, reference, template, and tool-output files that
surfaced /gsd:<cmd> as a user-typed slash command have been updated to
use /gsd-<cmd>, matching the Claude Code skill directory name.

Closes #2697

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-25 10:59:33 -04:00

1.8 KiB

name, description, argument-hint, allowed-tools
name description argument-hint allowed-tools
gsd:spike Spike an idea through experiential exploration, or propose what to spike next (frontier mode) [idea to validate] [--quick] [--text] or [frontier]
Read
Write
Edit
Bash
Grep
Glob
AskUserQuestion
WebSearch
WebFetch
mcp__context7__resolve-library-id
mcp__context7__query-docs
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 /gsd-new-project — auto-creates .planning/spikes/ if needed.

<execution_context> @/.claude/get-shit-done/workflows/spike.md @/.claude/get-shit-done/references/ui-brand.md </execution_context>

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

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).
Execute the spike workflow from @~/.claude/get-shit-done/workflows/spike.md end-to-end. Preserve all workflow gates (prior spike check, decomposition, research, risk ordering, observability assessment, verification, MANIFEST updates, commit patterns).