aim-test-driven-development

You can enforce test-driven development discipline by applying a strict test-first workflow that requires writing failing automated tests before any production code is implemented for new features, bug fixes, or behavior adjustments.

The RED-GREEN-REFACTOR cycle is a test-driven development workflow where you write a failing test first, implement production code to make the test pass, and then refactor the code while ensuring the tests continue to verify expected behavior.

To protect against regressions when adjusting behavior, write automated tests that define and verify expected behavior before implementing production code changes, ensuring observable failures exist prior to development.

Writing failing tests before production code ensures that your tests accurately define expected behavior and verify observable failures, preventing untested code from being introduced and maintaining strict development discipline.

No, you cannot implement production code before tests when following test-driven development discipline, because the protocol requires automated tests to verify behavior and fail observably before any implementation begins.

You need to follow the aim-writing-tests protocol for regression testing whenever you are implementing new features, fixing defects, or adjusting behavior, ensuring automated tests define expected outcomes before production code is written.