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: API/Integration Examples: Performance Examples: Architecture Examples: One Question Per Spike: Each document focuses on a single technical decision or research question Time-Boxed Research: Define specific time limits and deliverables for each spike Evidence-Based Decisions: Require concrete evidence (tests, prototypes, documentation) before marking as complete Clear Recommendations: Document specific recommendations and rationale for implementation Dependency Tracking: Identify how spikes relate to each other and impact project decisions Outcome-Focused: Every spike must result in an actionable decision or recommendation Focus on time-boxed research that resolves critical technical decisions and unblocks development progress. - Third-party API capabilities and limitations - Integration patterns and authentication - Rate limits and performance...