XP-style spike — time-boxed experiment on an isolated branch; code is disposable. Answer one technical or design question (feasibility, library fit, performance bound, integration). Use automated checks only when they help prove the goal — no delivery test pyramid, no ATDD/TDD discipline on the spike branch. Explicit promotion to skills/atdd, skills/tdd, or skills/legacy-testing when learning is done. Use for unknowns before committing to product work, not for shipping features.
$npx -y skills add dan-the-dev/xp-developer-skills --skill spikeInstalls into the current project.
Run `npx skills use "https://github.com/dan-the-dev/xp-developer-skills" --skill "dan-the-dev/xp-developer-skills/spike"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/dan-the-dev/xp-developer-skills" that are relevant to the current task. Run `npx skills add "https://github.com/dan-the-dev/xp-developer-skills"` and select the relevant skills, then follow their instructions.