Create spike definitions with canonical names and numbered approaches for parallel exploratory implementation. Use when partner has an underdefined feature idea and wants to explore multiple implementation approaches in parallel, when uncertain which technical approach is best, or when comparing alternatives before committing to implementation
Install
npx skills add jlindley/jlindley-skills --skill defining-spikesnpx skills add jlindley/jlindley-skills --skill defining-spikes -a claude-code -gnpx skills add jlindley/jlindley-skills --skill defining-spikes -a codex -ggemini skills install https://github.com/jlindley/jlindley-skills.git --path skills/defining-spikesgh skill install jlindley/jlindley-skills defining-spikesgit clone --depth 1 https://github.com/jlindley/jlindley-skills /tmp/jlindley__jlindley-skills
mkdir -p ~/.claude/skills ~/.agents/skills
cp -R /tmp/jlindley__jlindley-skills/skills/defining-spikes ~/.claude/skills/defining-spikes # Claude Code
cp -R /tmp/jlindley__jlindley-skills/skills/defining-spikes ~/.agents/skills/defining-spikes # Codex, Cursor, Gemini CLI, Copilot, OpenCode