When building software, teams face hard questions. A technical spike document helps answer them before writing code. It is a time-boxed research task focused on a single critical decision.
Each spike has a clear goal and deadline. It lists research questions, tasks, and success criteria. The findings lead to a clear recommendation. This helps teams make informed choices faster.
Anyone working on a development team can use this skill. It keeps research organized and prevents delays. The result is better architecture and fewer surprises.
Global
mkdir -p ~/.claude/skills/create-technical-spikeProject
mkdir -p .claude/skills/create-technical-spikeSource Repository
Lark Baselarksuite/cli
Simplify your Lark Base data with tables, fields, records, and views
Lark Wikilarksuite/cli
Manage your Lark Wiki spaces, members, and documents with simple commands
Grillingmattpocock/skills
Test your plan thoroughly with clear step-by-step interview questions
Analyze Projectlllllllama/rigorpilot-skills
Safe read-only analysis of deep learning repos for understanding and risk detection
Ai Research Reproductionlllllllama/rigorpilot-skills
Faithful reproduction of deep learning research with auditable steps and minimal changes
Repo Intake And Planlllllllama/rigorpilot-skills
Scan a repo, find commands, and get a simple reproduction plan
Minimal Run And Auditlllllllama/rigorpilot-skills
Capture evidence from deep learning runs and create standardized audit reports
Obsidian Vaultmattpocock/skills
Search create and organize notes with wikilinks and index notes easily