From GSD Core
Spikes an idea through experiential exploration, building focused experiments to validate feasibility and produce verified knowledge for the real build.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gsd-core:gsd-spike [idea to validate] [--quick] [--text] [--wrap-up] or [frontier][idea to validate] [--quick] [--text] [--wrap-up] or [frontier]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<objective>
Two modes:
Does not require prior new-project setup — auto-creates .planning/spikes/ if needed.
<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>
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.
Preserve all workflow gates (prior spike check, decomposition, research, risk ordering, observability assessment, verification, MANIFEST updates, commit patterns).
npx claudepluginhub open-gsd/gsd-coreRuns an exploratory spike to test technical assumptions before committing to a full implementation. Works with or without an existing Implan plan. Produces a spike report for the user or implementing agent.
Conducts time-boxed spikes to resolve open questions via collaborative research and throwaway prototypes. Records outcomes on work items.
Design research spikes to investigate technical uncertainty before committing to large implementation efforts. Use when feasibility is unclear or approach is unproven.