Spike
A short, disposable technical experiment from Extreme Programming used to answer a technical question or reduce uncertainty before formal development. It deliberately does not aim for mergeable code quality, only to verify whether a target path works; the code is discarded on failure.
Timeline (last 90 days)
In the two-run spike protocol, the kill criteria should be checked by a script, because the person running the spike is precisely the one most motivated to keep it alive.
The term Spike comes from Extreme Programming, originally referring to using a short, disposable experiment to answer a technical question or reduce uncertainty before formal development.
A Spike deliberately does not pursue mergeable code quality, only the single piece of information of "whether it can work"; a prototype, by contrast, is written to evolve into a product. The practical criterion for distinguishing the two is: if you would delete the code after the exploration fails, then it is a Spike.
In the spike script, 'timeout' measures wall-clock time, so a run stuck on a prompt cannot borrow time from the next run.
In the spike protocol, the two runs should share the same 90-minute clock, and neither run gets a private 90 minutes.
The starting points of the two runs must be completely identical and mutually non-interfering, and using git worktree can turn this discipline from a verbal promise into a mechanical guarantee.
Spike 是敏捷开发中在正式开发前用最小成本验证技术可行性的短期实验
All Facts (7)
In the two-run spike protocol, the kill criteria should be checked by a script, because the person running the spike is precisely the one most motivated to keep it alive.
50%UnverifiedThe term Spike comes from Extreme Programming, originally referring to using a short, disposable experiment to answer a technical question or reduce uncertainty before formal development.
50%UnverifiedA Spike deliberately does not pursue mergeable code quality, only the single piece of information of "whether it can work"; a prototype, by contrast, is written to evolve into a product. The practical criterion for distinguishing the two is: if you would delete the code after the exploration fails, then it is a Spike.
50%UnverifiedIn the spike script, 'timeout' measures wall-clock time, so a run stuck on a prompt cannot borrow time from the next run.
50%UnverifiedIn the spike protocol, the two runs should share the same 90-minute clock, and neither run gets a private 90 minutes.
50%UnverifiedThe starting points of the two runs must be completely identical and mutually non-interfering, and using git worktree can turn this discipline from a verbal promise into a mechanical guarantee.
50%UnverifiedSpike 是敏捷开发中在正式开发前用最小成本验证技术可行性的短期实验
50%