Test-Driven Development

Write the proof first. If the proof never failed, it may not prove anything.

Activation

Use this for code that is meant to remain: features, bug fixes, refactors, test harnesses, scripts, offensive tooling, parsers, and skill utilities.

Disposable exploration is allowed only as a spike. Do not ship, commit, or claim reliability from spike code until behavior is captured by a test, reproducer, or explicit verification gate.

RED-GREEN-REFACTOR

1. RED: write one minimal test or reproducer for desired behavior or the bug.
2. Verify RED: run it and confirm it fails for the expected reason.
3. GREEN: implement the smallest code that makes it pass.
4. Verify GREEN: run the focused check and relevant broader checks.
5. REFACTOR: clean structure while checks stay green.
6. Repeat: one behavior at a time.