develop-spike-summary

1<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
2# Spike Summary
3 
4A 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.
5 
6## When to Use
7 
8- After completing a time-boxed technical exploration
9- When evaluating technology choices or vendor options
10- After proof-of-concept work that needs to inform team decisions
11- When investigating feasibility of a proposed solution
12- Before committing engineering resources to a new approach
13 
14## When NOT to Use
15 
16- You are recording the resulting architecture decision itself -> use `develop-adr`; the spike informs, the ADR decides
17- The exploration was user research, not technical or design feasibility -> use `discover-interview-synthesis`
18- You want to propose the solution the spike pointed to -> use `develop-solution-brief`
19- The spike has not happened yet: this skill documents results; time-box and run the exploration first
20 
21## Instructions
22 
23When asked to document a spike, follow these steps:
24 
251. **State the Question Clearly**
26…