
Tdd Workflow
- 295 installs
- 30.1k repo stars
- Updated August 4, 2026
- davila7/claude-code-templates
tdd-workflow is a Claude Code skill that runs test-driven development red-green-refactor cycles—write failing tests first, implement minimal code, refactor safely, and keep suites fast across unit and integration layers.
About
tdd-workflow is a skill from davila7/claude-code-templates that encodes Test-Driven Development principles for Claude Code agents. It follows the RED → GREEN → REFACTOR loop and the three TDD laws: production code only to pass failing tests, minimal test code to show failure, and minimal implementation to go green. Allowed tools include Read, Write, Edit, Glob, Grep, and Bash so agents can create tests, implement code, and run suites quickly. Developers reach for tdd-workflow when they want agent-enforced TDD instead of bolting tests on after features land.
- Enforces red-green-refactor sequencing
- Scopes minimal tests before implementation
- Balances unit vs integration coverage
- Keeps refactors safe with passing suites
Tdd Workflow by the numbers
- 295 all-time installs (skills.sh)
- +1 installs in the week ending Jul 5, 2026 (Skillselion tracking)
- Ranked #708 of 2,153 Testing & QA skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davila7/claude-code-templates --skill tdd-workflowAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 295 |
|---|---|
| repo stars | ★ 30.1k |
| Last updated | August 4, 2026 |
| Repository | davila7/claude-code-templates ↗ |
How do you run TDD red-green-refactor in Claude?
Run red-green-refactor cycles: write failing tests first, implement minimal code, refactor safely, and keep suites fast across units and integration layers.
Who is it for?
Developers who want Claude Code to enforce strict TDD discipline on new features with Read, Write, Edit, Glob, Grep, and Bash.
Skip if: Exploratory spikes with no clear behavior spec or legacy codebases where characterization tests are not yet feasible.
When should I use this skill?
User asks for TDD, red-green-refactor, test-first development, or failing tests before implementation.
What you get
Failing tests, minimal passing implementation, refactored production code, and fast-running unit and integration test suites.
- failing tests
- passing implementation
- refactored code
By the numbers
- Documents 3 TDD laws governing minimal test and production code
- Defines 3-phase RED → GREEN → REFACTOR cycle
Files
TDD Workflow
Write tests first, code second.
---
1. The TDD Cycle
🔴 RED → Write failing test
↓
🟢 GREEN → Write minimal code to pass
↓
🔵 REFACTOR → Improve code quality
↓
Repeat...---
2. The Three Laws of TDD
1. Write production code only to make a failing test pass 2. Write only enough test to demonstrate failure 3. Write only enough code to make the test pass
---
3. RED Phase Principles
What to Write
| Focus | Example |
|---|---|
| Behavior | "should add two numbers" |
| Edge cases | "should handle empty input" |
| Error states | "should throw for invalid data" |
RED Phase Rules
- Test must fail first
- Test name describes expected behavior
- One assertion per test (ideally)
---
4. GREEN Phase Principles
Minimum Code
| Principle | Meaning |
|---|---|
| YAGNI | You Aren't Gonna Need It |
| Simplest thing | Write the minimum to pass |
| No optimization | Just make it work |
GREEN Phase Rules
- Don't write unneeded code
- Don't optimize yet
- Pass the test, nothing more
---
5. REFACTOR Phase Principles
What to Improve
| Area | Action |
|---|---|
| Duplication | Extract common code |
| Naming | Make intent clear |
| Structure | Improve organization |
| Complexity | Simplify logic |
REFACTOR Rules
- All tests must stay green
- Small incremental changes
- Commit after each refactor
---
6. AAA Pattern
Every test follows:
| Step | Purpose |
|---|---|
| Arrange | Set up test data |
| Act | Execute code under test |
| Assert | Verify expected outcome |
---
7. When to Use TDD
| Scenario | TDD Value |
|---|---|
| New feature | High |
| Bug fix | High (write test first) |
| Complex logic | High |
| Exploratory | Low (spike, then TDD) |
| UI layout | Low |
---
8. Test Prioritization
| Priority | Test Type |
|---|---|
| 1 | Happy path |
| 2 | Error cases |
| 3 | Edge cases |
| 4 | Performance |
---
9. Anti-Patterns
| ❌ Don't | ✅ Do |
|---|---|
| Skip the RED phase | Watch test fail first |
| Write tests after | Write tests before |
| Over-engineer initial | Keep it simple |
| Multiple asserts | One behavior per test |
| Test implementation | Test behavior |
---
10. AI-Augmented TDD
Multi-Agent Pattern
| Agent | Role |
|---|---|
| Agent A | Write failing tests (RED) |
| Agent B | Implement to pass (GREEN) |
| Agent C | Optimize (REFACTOR) |
---
Remember: The test is the specification. If you can't write a test, you don't understand the requirement.
Related skills
How it compares
Pick tdd-workflow when you want agent-enforced test-first discipline; use generic testing skills when adding tests after features exist.
FAQ
What is the TDD cycle in tdd-workflow?
tdd-workflow follows RED → GREEN → REFACTOR: write a failing test, add minimal code to pass, then improve design without changing behavior. The skill also encodes the three TDD laws limiting premature production and test code.
Which tools does tdd-workflow allow?
tdd-workflow allows Read, Write, Edit, Glob, Grep, and Bash so Claude Code agents can author tests, edit implementation files, search the codebase, and execute test commands during the cycle.