tdd-workflow
Test-driven development discipline: RED (failing test) → GREEN (minimal code) → REFACTOR, delete-and-restart if production code was written first, and the test-type taxonomy (integration for API surfa
Files1
View on GitHubSKILL.mdinternal/builtins/universal/testing/skills/tdd-workflow/SKILL.md
GitHub- Write the test before the code. Update the test when changing behaviour.
- Fixing a bug: write the failing test first, then fix. RED → GREEN → REFACTOR.
- Wrote production code before the test? Delete it and start over — no exceptions, don't keep it as reference.
- Integration tests for API surfaces, unit tests for business logic, property tests for edge-case-heavy code.
- Run the full test suite before committing — never push untested code.
- Run the new test and confirm it fails for the right reason before writing the fix.
- If a test cannot be made to pass after three attempts, stop and report rather than skipping or weakening it.