create-technical-spike
Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.
Profile →npx skills add github/awesome-copilot --skill create-technical-spike --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Create Technical Spike Document Create time-boxed technical spike documents for researching critical questions that must be answered before development can proceed. Each spike focuses on a specific technical decision with clear deliverables and timelines. ## Document Structure Create individual files in `${input:FolderPath|docs/spikes}` directory. Name each file using the pattern: `[category]-[short-description]-spike.md` (e.g., `api-copilot-integration-spike.md`, `performance-realtime-audio-spike.md`). ```md --- title: "${input:SpikeTitle}" category: "${input:Category|Technical}" status: "🔴 Not Started" priority: "${input:Priority|High}" timebox: "${input:Timebox|1 week}" created: [YYYY-MM-DD] updated: [YYYY-MM-DD] owner: "${input:Owner}" tags: ["technical-spike", "${input:Category|technical}", "research"] --- # ${input:SpikeTitle} ## Summary **Spike Objective:** [Clear, specific question or decision that needs resolution] **Why This Matters:** [Impact on development/architecture decisions] **Timebox:** [How much time allocated to this spike] **Decision Deadline:** [When this must be resolved to avoid blocking development] ## Research Question(s) **Primary Question:** [Main tec
- Document Structure
- Categories for Technical Spikes
- API Integration
- Architecture & Design
- Performance & Scalability
- Platform & Infrastructure
- Security & Compliance
- User Experience
- File Naming Conventions
- Best Practices for AI Agents
- Research Strategy
- Phase 1: Information Gathering
- Phase 2: Validation & Testing
- Phase 3: Decision & Documentation
What does the create-technical-spike skill do?
Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.
How do I install it?
Run `npx skills add github/awesome-copilot --skill create-technical-spike --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.