msd-core/commands/gsd/spike.md at a60e05c714e11d5d6b5ffdc842b272dd9eb73b06

Files

Tom Boucher a60e05c714 fix(claude): restore namespaced /gsd:<command> references (#3452 )

* fix(claude): restore namespaced /gsd:<command> references

* test(claude): align slash-command expectations to /gsd: form

* test(claude): align generated command references to /gsd:

* test(claude): finish /gsd: namespace expectation updates

2026-05-12 21:53:24 -04:00

2.1 KiB

Raw Blame History

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] [--wrap-up] 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/workflows/spike-wrap-up.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).
--wrap-up — Package spike findings into a persistent project skill for future build conversations. Runs the spike-wrap-up workflow.

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).

2.1 KiB Raw Blame History

2.1 KiB

Raw Blame History