Implement

1. Write the minimum production code to make the failing test pass. No extra features, no premature abstractions.
2. Run the test suite. Confirm all tests pass.
   • Show the test output to the user.
   • If tests fail, fix the production code, not the test.
3. Commit with a feat or fix-type conventional commit message.

Phase 3 — Refactor

1. Review the code just written. Look for:
   • Duplication
   • Unclear naming
   • Overly complex logic
   • Missing type safety
   • Opportunities to extract helpers or simplify
2. If refactoring is needed:
   • Make changes.
   • Re-run the test suite. Confirm all tests still pass.
   • Commit with a refactor-type conventional commit message.
3. If no refactoring is needed, explicitly state why and skip the commit.

After the Cycle

Ask the user: "Continue with another test case, or is this implementation complete?"

If continuing, repeat from Phase 1.

Constraints

• Never skip the Red phase. Every piece of production code must be preceded by a failing test.
• Never write production code and tests in the same step. They are always separate commits.
• Each phase gets its own commit. This is non-negotiable.
• Use the project's existing test framework. Do not introduce a new one without asking.