create-technical-spike

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.

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).

Use descriptive, kebab-case names that indicate the category and specific unknown:

Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation. Source: github/awesome-copilot.