Tdd

Forces you to write tests before code, then implements just enough to pass them. The workflow runs plan-agent to design test cases, arbiter to write failing tests, kraken to implement minimal code, then arbiter again to validate. It's strict about the red-green-refactor cycle with no exceptions allowed. The philosophy guide is uncompromising: if you wrote code before watching a test fail, delete it and start over. Best for features where you need coverage guarantees or want to avoid debugging sessions later. The "delete means delete" stance and table of rationalizations are blunt but useful if you keep cutting corners on TDD discipline.

skills.sh installs: 472
GitHub stars: 3.9K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add parcadei/continuous-claude-v3 --skill tdd --agent claude-code

Installs into .claude/skills of the current project.

Files

/tdd - Test-Driven Development Workflow

Strict TDD workflow: tests first, then implementation.

When to Use

"Implement X using TDD"
"Build this feature test-first"
"Write tests for X then implement"
Any feature where test coverage is critical
Bug fixes that need regression tests

TDD Philosophy

Overview

Write the test first. Watch it fail. Write minimal code to pass.

Core principle: If you didn't watch the test fail, you don't know if it tests the right thing.

Violating the letter of the rules is violating the spirit of the rules.

The Iron Law

NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST

Write code before the test? Delete it. Start over.

No exceptions:

Don't keep it as "reference"
Don't "adapt" it while writing tests
Don't look at it
Delete means delete

Implement fresh from tests. Period.

Red-Green-Refactor

RED - Write Failing Test

Write one minimal test showing what should happen.

Good:

test('retries failed operations 3 times', async () => {
  let attempts = 0;
  const operation = () => {
    attempts++;
    if (attempts < 3) throw new Error('fail');
    return 'success';
  };

SKILL.md on GitHub