Tdd Workflow

Test-driven development for: $ARGUMENTS

ThanaritKanjanametawatAU updated 1y ago
Claude CodeGeneric
View source ↗
Test-driven development for: $ARGUMENTS

1. WRITE TESTS FIRST
   - Write comprehensive tests for $ARGUMENTS
   - Cover expected inputs/outputs
   - Include edge cases
   - DO NOT create mock implementations

2. VERIFY TESTS FAIL
   - Run tests and confirm they fail
   - DO NOT write implementation code yet

3. COMMIT TESTS
   - git add test files
   - git commit -m "Add tests for $ARGUMENTS"

4. IMPLEMENT TO PASS
   - Write minimal code to pass tests
   - DO NOT modify the tests
   - Iterate until all tests pass
   - Use subagents to verify not overfitting

5. COMMIT IMPLEMENTATION
   - git add implementation
   - git commit -m "Implement $ARGUMENTS"

Maintain Tdd Workflow?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

[Tdd Workflow on getagentictools](https://getagentictools.com/loops/thanaritkanjanametawatau-tdd-workflow?ref=badge)
npx agentictools info loops/thanaritkanjanametawatau-tdd-workflow

The second line is the CLI lookup for this page — handy in READMEs and docs.