Run throwaway prototypes to validate feasibility
spikeskillsetup L1★377,536
openclaw/openclaw ↗What it does
Run throwaway prototypes to validate feasibility or compare approaches
Best for
Test technical risk before committing to production without burning weeks
Inputs
- · Feasibility question
- · optional: competing approaches (A/B)
- · optional: edge case to stress-test
Outputs
- · Verdict (VALIDATED/PARTIAL/INVALIDATED)
- · evidence (exact commands/measurements)
- · recommendation (ship/adjust/avoid)
Requires
- · Any build tools relevant to the spike (minimal)
- · no package sprawl or Docker
Preconditions
Clear feasibility question; external deps health-checked before build
Failure modes
External dep unavailable; spike code doesn't isolate question; edge case missed; invalidated verdict blocks shipping
Trust signals
- · Smallest runnable artifact
- · Edge case testing
- · Verdict template enforced
- · repo-local output (spikes/NNN-slug/)