test-driven-development
obra/superpowers
Detailed guidance for a strict test-driven development cycle: write a failing test first, confirm the failure, add minimal code to pass, refactor cleanly, and repeat so every feature, fix, or refactor ships with confidence.