create-technical-spike

# 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 technical question that needs answering] **Secondary Questions:** - [Related question 1] - [Related question 2] - [Related question 3] ## Investigation Plan ### Research Tasks - [ ] [Specific research task 1] - [ ] [Specific research task 2] - [ ] [Specific research task 3] - [ ] [Crea...