tdd-workflow
Guides the development process using the strict Test-Driven Development (TDD) cycle.
Install
mkdir -p .claude/skills/tdd-workflow-javiertarazon && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15136" && unzip -o skill.zip -d .claude/skills/tdd-workflow-javiertarazon && rm skill.zipInstalls to .claude/skills/tdd-workflow-javiertarazon
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.Key capabilities
- →Write failing tests first (RED phase)
- →Implement minimal code to pass tests (GREEN phase)
- →Refactor code to improve quality (REFACTOR phase)
- →Apply the AAA pattern for test structure
- →Prioritize test cases (happy path, error, edge cases)
- →Identify TDD anti-patterns
How it works
The skill guides through the RED-GREEN-REFACTOR cycle, starting with writing a failing test, then implementing the minimum code to make it pass, and finally refactoring the code.
Inputs & outputs
When to use tdd-workflow
- →Practicing TDD during development
- →Refactoring code while maintaining tests
- →Ensuring test coverage for new features
About this skill
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
- Write production code only to make a failing test pass
- Write only enough test to demonstrate failure
- 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.
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
When not to use it
- →The task is exploratory development
- →The task involves UI layout
Limitations
- →The skill is not suitable for exploratory development
- →It is not designed for UI layout tasks
How it compares
This skill enforces a structured, iterative development process by dictating the order of test writing, code implementation, and refactoring, unlike an unstructured coding approach.
Compared to similar skills
tdd-workflow side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| tdd-workflow (this skill) | 0 | 5mo | No flags | Beginner |
| code-assist | 1 | 5mo | No flags | Advanced |
| moonbit-agent-guide | 1 | 7mo | Review | Intermediate |
| ruby-pro | 1 | 4mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by javiertarazon
View all by javiertarazon →You might also like
code-assist
mikeyobrien
Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and TDD Coach — following existing patterns, avoiding over-engineering, and producing idiomatic, modern code.
moonbit-agent-guide
loro-dev
Guide for writing, refactoring, and testing MoonBit projects. Use when working in MoonBit modules or packages, organizing MoonBit files, using moon tooling (build/check/test/doc/ide), or following MoonBit-specific layout, documentation, and testing conventions.
ruby-pro
sickn33
Write idiomatic Ruby code with metaprogramming, Rails patterns, and performance optimization. Specializes in Ruby on Rails, gem development, and testing frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or complex Ruby features.
agent-implementer-sparc-coder
ruvnet
Agent skill for implementer-sparc-coder - invoke with $agent-implementer-sparc-coder
intellij-mcp
navikt
Uses the IntelliJ MCP tools for various programming tasks. Use when the IntelliJ MCP is available and you are building, running tests, searching or refactoring.
apex
zuzu59
Systematic implementation using APEX methodology (Analyze-Plan-Execute-eXamine) with parallel agents, self-validation, and optional adversarial review. Use when implementing features, fixing bugs, or making code changes that benefit from structured workflow.