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

Files

Lex Christopherson a95cabaedb fix: sync spike/sketch workflows with upstream skill improvements

Spike workflow:
- Add prior spike check — skips already-validated questions
- Add comparison spikes (NNN-a/NNN-b) for head-to-head evaluation
- Add research-before-building step (context7 + web search)
- Add forensic logging/observability for runtime-interactive spikes
- Add Type column to MANIFEST, type/Research/Observability to README

Sketch workflow:
- Add research-the-target-stack step — check component availability,
  framework constraints, and idiomatic patterns before building

Spike wrap-up workflow:
- Replace per-spike curation with auto-include-all (every spike carries
  signal: VALIDATED=patterns, PARTIAL=constraints, INVALIDATED=landmines)
- Add Step 10 intelligent routing — integration spike candidates,
  frontier spike candidates, and standard next-step options

Commands updated with context7/WebSearch tools and --text flag.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-20 14:04:31 -06:00

1.5 KiB

Raw Blame History

name, description, argument-hint, allowed-tools

name

description

argument-hint

allowed-tools

gsd:spike

Rapidly spike an idea with throwaway experiments to validate feasibility before planning

<idea to validate> [--quick] [--text]

Read

Write

Edit

Bash

Grep

Glob

AskUserQuestion

WebSearch

WebFetch

mcp__context7__resolve-library-id

mcp__context7__query-docs

Rapid feasibility validation through focused, throwaway experiments. Each spike answers one specific question with observable evidence. Spikes live in `.planning/spikes/` and integrate with GSD commit patterns, state tracking, and handoff workflows.

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

1.5 KiB Raw Blame History

1.5 KiB

Raw Blame History