A spike is a time-boxed experiment to answer a question ("does this API work like I think?", "is this approach viable?"). Its only output is knowledge — the code is disposable.

State the question. Write down exactly what you're trying to learn. The spike is done when it's answered, not when the code "works".
Go fast and dirty. Skip tests, error handling, and polish. Hardcode. The point is to learn, not to ship — don't invest in code you'll throw away.
Time-box it. Set a bound. If you blow past it, you've learned the problem is harder than expected — that's itself an answer; report it.
Capture the finding. Record what you learned (and consider saving it as a skill or memory if it'll recur).
THROW THE CODE AWAY. Delete the spike. Then build the real thing from scratch with test-driven-development — do NOT "clean up" the spike into production code; it carries hidden assumptions and skipped cases.

Red flag: a spike quietly becoming the implementation. Delete means delete.

Más de este repositorio

mismo repositorio

react-doctor

New1Direction/korgex

Catch bad React in your changes — run react-doctor's deterministic scan and fix what it flags

2026-06-055

security-scan

New1Direction/korgex

Run a verifiable security scan (vulns, secrets, misconfig) over code you wrote or deps you added, before calling the work done

2026-06-035

browser-automation

New1Direction/korgex

Drive a real browser verifiably — navigate, snapshot, act BY INDEX, extract; every step provable

2026-06-025

verifiable-orchestration

New1Direction/korgex

Run multi-agent work as ONE provable causal DAG — parallel subagents, an Orchestrate graph, an immutable spec-seed

2026-06-025

building-an-mcp-server

New1Direction/korgex

Author or connect a Model Context Protocol server so an agent gains new tools

2026-06-015

ci-cd-pipelines

New1Direction/korgex

Build automated pipelines that gate merges and ship reliably

2026-06-015

name	spike
description	Throwaway exploration to learn the unknown, then delete it and build it properly
version	1
trust	built-in

A spike is a time-boxed experiment to answer a question ("does this API work like I think?", "is this approach viable?"). Its only output is knowledge — the code is disposable.

State the question. Write down exactly what you're trying to learn. The spike is done when it's answered, not when the code "works".
Go fast and dirty. Skip tests, error handling, and polish. Hardcode. The point is to learn, not to ship — don't invest in code you'll throw away.
Time-box it. Set a bound. If you blow past it, you've learned the problem is harder than expected — that's itself an answer; report it.
Capture the finding. Record what you learned (and consider saving it as a skill or memory if it'll recur).
THROW THE CODE AWAY. Delete the spike. Then build the real thing from scratch with test-driven-development — do NOT "clean up" the spike into production code; it carries hidden assumptions and skipped cases.

Red flag: a spike quietly becoming the implementation. Delete means delete.