minimal-coder

To generate minimal code to pass a failing test, you provide the failing test case and your current implementation to generate only the necessary code for the TDD red-to-green phase. This focuses entirely on speed and simplicity without immediate optimization or refactoring.

The minimal code approach for quick prototyping involves writing the absolute minimum code required to satisfy a given test case. It applies to spike implementations, allowing you to iterate quickly by making tests pass without premature optimization or refactoring.

Yes, you need to provide the failing test and the current implementation as input. The tool uses these inputs to produce only the necessary code required to make that specific test pass during the red-to-green phase.

You should avoid minimal code generation when your primary goal involves optimization, refactoring, or building production-ready architecture. It is designed strictly for speed-focused prototyping and moving quickly from a failing test to a passing one.