gsd:spike
Spike an idea through experiential exploration, or propose what to spike next (frontier mode)
Profile →npx skills add davepoon/buildwithclaude --skill spike --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
<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 `/gsd:new-project` — auto-creates `.planning/spikes/` if needed. </objective> <execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/spike.md @${CLAUDE_PLUGIN_ROOT}/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). </context> <process> Execute the spike workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/s
What does the gsd:spike skill do?
Spike an idea through experiential exploration, or propose what to spike next (frontier mode)
How do I install it?
Run `npx skills add davepoon/buildwithclaude --skill spike --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From davepoon/buildwithclaude, a repository with 3,251 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.