minimal-impl-generator

To make failing tests pass in TDD, implement the simplest working code that satisfies test expectations without premature optimization. This green-phase approach directs engineers to create minimal runnable files using repository tools, focusing only on tested behavior before moving to refactoring later.

The minimal implementation approach for the TDD green phase is writing the smallest code change required to satisfy failing tests. It prevents over-engineering by directing engineers to create only the behavior tests require, producing runnable files in the repository for verification.

To implement code to pass tests using an engineer agent, create minimal implementation files in the repository using create_file or replace_string_in_file tools. This ensures implementations are testable and persistent, then run the test suite to confirm they pass.

Use YAGNI principles in test-driven development during the implementation phase when tests exist and code must satisfy test expectations. Apply YAGNI when feature tests are written, implementing only the behavior tests require before moving to later refactoring.

Yes, existing tests are required before generating a minimal implementation. This Skill is applicable during implementation phases and feature workflows where tests already exist and code must satisfy test expectations, producing runnable files for verification.

Test-driven development implementations may keep failing if code exceeds minimal requirements or misses tested behavior. Focus on the smallest change that makes failing tests pass, create files using workspace tools, and run the test suite to confirm they pass before refactoring.