It may make not much sense until you read it in the context of Scrum or Agile software development.
According to Wikipedia, spike is:
A time boxed period used to research a concept or create a simple prototype. Spikes can either be planned to take place in between sprints or, for larger teams, a spike might be accepted as one of many sprint delivery objectives. Spikes are often introduced before the delivery of large or complex product backlog items in order to secure budget, expand knowledge, or produce a proof of concept. The duration and objective(s) of a spike is agreed between product owner and development team before the start. Unlike sprint commitments, spikes may or may not deliver tangible, shippable, valuable functionality. For example, the objective of a spike might be to successfully reach a decision on a course of action. The spike is over when the time is up, not necessarily when the objective has been delivered.
The use of Spike on { how to / replacing } in the records you found is just the use of spike as a verb, which basically means "research a concept or create a prototype". Your guess is really close!