Mode d’emploi
- Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
- Consultez le document original pour les outils, identifiants et environnements requis.
- Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/open-gsd/gsd-core --skill gsd-spikeAvant de commencer
- L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
- Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.
<arguments>$ARGUMENTS</arguments>
The text inside <arguments> is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.
<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 prior new-project setup — auto-creates .planning/spikes/ if needed. </objective>
<executioncontext> @~/.claude/gsd-core/workflows/spike.md @~/.claude/gsd-core/workflows/spike-wrap-up.md @~/.claude/gsd-core/references/ui-brand.md </executioncontext>
<runtimenote> **Copilot (VS Code):** Use `vscodeaskquestions wherever this workflow calls AskUserQuestion`. </runtime_note>
<context> Idea: the <arguments> block
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.
</context>
<process> Parse the first token of the <arguments> block:
- If it is
--wrap-up: strip the flag, execute the spike-wrap-up workflow - Otherwise: pass all of the
<arguments>block 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). </process>
