Files
msd-core/commands/gsd/spike.md
Tom Boucher 73c1af5168 fix(#2543): replace legacy /gsd-<cmd> syntax with /gsd:<cmd> across all source files (#2595)
Commands are now installed as commands/gsd/<name>.md and invoked as
/gsd:<name> in Claude Code. The old hyphen form /gsd-<name> was still
hardcoded in hundreds of places across workflows, references, templates,
lib modules, and command files — causing "Unknown command" errors
whenever GSD suggested a command to the user.

Replace all /gsd-<cmd> occurrences where <cmd> is a known command name
(derived at runtime from commands/gsd/*.md) using a targeted Node.js
script. Agent names, tool names (gsd-sdk, gsd-tools), directory names,
and path fragments are not touched.

Adds regression test tests/bug-2543-gsd-slash-namespace.test.cjs that
enforces zero legacy occurrences going forward. Removes inverted
tests/stale-colon-refs.test.cjs (bug #1748) which enforced the now-obsolete
hyphen form; the new bug-2543 test supersedes it. Updates 5 assertion
tests that hardcoded the old hyphen form to accept the new colon form.

Closes #2543

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-22 12:04:25 -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).