develop-spike-summary

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # Spike Summary A spike summary documents the results of a time-boxed exploration . a focused investigation to reduce uncertainty before committing to implementation. Spikes answer specific questions like "Can we integrate with this API?" or "Is this technology viable for our use case?" The summary captures findings so the team can make informed decisions without the spike participants needing to repeat explanations. ## When to Use - After completing a time-boxed technical exploration - When evaluating technology choices or vendor options - After proof-of-concept work that needs to inform team decisions - When investigating feasibility of a proposed solution - Before committing engineering resources to a new approach ## Instructions When asked to document a spike, follow these steps: 1. **State the Question Clearly** Articulate the specific question the spike was designed to answer. Good spike questions are focused and answerable with the time-box available. If the question evolved during the spike, document both the original and final versions. 2. **Define the Time-Box** Document the time allocated (e.g., 3 days) and actual time spent. If the spike exceeded its time-box, explain why and note any remaining work. 3. **Describe the Approach** Explain what was tried, in what order, and why. This helps future readers understand the methodology and whether alternative approaches were...