What problem does it solve? Development teams often face unresolved technical questions that block implementation, and without a structured research process these decisions get made ad hoc or delayed indefinitely. This Skill produces standardized, time-boxed spike documents that capture research questions, investigation plans, findings, and actionable recommendations. ## Core Features & Use Cases - Structured Spike Template: Generates a complete Markdown spike document with sections for research questions, investigation plans, success criteria, findings, decisions, and status history. - Category-Based Organization: Supports spike categories including API integration, architecture, performance, platform, security, and user experience, with kebab-case file naming conventions. - Phased Research Strategy: Guides a three-phase workflow of information gathering, prototype validation, and decision documentation. - Use Case: Before integrating a third-party speech API, create an api-azure-speech-realtime-spike.md document that time-boxes the investigation to one week, defines success criteria, and ends with a clear recommendation for the team. ## Quick Start Create a technical spike document in docs/spikes for evaluating whether the Copilot chat API supports our real-time integration requirements, time-boxed to one week.
