test-driven-development skill
✓ VerifiedImplements features and bugfixes using the Red-Green-Refactor cycle by writing failing tests before any production code.
- GitHub stars
- 5
- Files
- 2
- Last commit
- Oct 29, 2026
- License
- MIT
- Allowed tools
- —
What does the test-driven-development skill do?
test-driven-development implements features and bugfixes using the Red-Green-Refactor cycle by writing failing tests before any production code.
Summary generated from the skill's SKILL.md.
About the test-driven-development skill
Developers implementing new features, fixing bugs, or performing refactors can use this skill to follow a strict Red-Green-Refactor cycle. The process requires writing a single, minimal failing test before any production code is written. This ensures that every change is verified by a test that actually catches a failure rather than just passing immediately.
An agent should load this skill whenever a task involves behavior changes or code improvements. The workflow relies on executing test commands like npm test, pytest, or cargo test to verify the state of the codebase. The agent produces minimal, functional code that satisfies the specific test requirements without over-engineering or adding unnecessary features. By strictly adhering to the rule of deleting any implementation code written before a failing test, the skill ensures high confidence and prevents regressions through a disciplined development loop.
What an agent can do with it
- 1Implement a new featureCreate a new function by first writing a minimal test that describes the desired behavior and watching it fail.
- 2Fix a software bugReproduce a bug by writing a failing test that captures the error before writing the fix.
- 3Verify codebase integrityRun the full project test suite to ensure that new changes have not caused regressions in unrelated areas.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the test-driven-development skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the test-driven-development skill in Plugin
/plugin marketplace add KunanonJ/superstacks /plugin install superstacks@superstacks
Install the test-driven-development skill in Claude Code
~/.claude/skills/test-driven-development/SKILL.md
$ npx degit KunanonJ/superstacks/plugins/superstacks/skills/test-driven-development ~/.claude/skills/test-driven-developmentInstall the test-driven-development skill in Claude Code (project)
.claude/skills/test-driven-development/SKILL.md
$ npx degit KunanonJ/superstacks/plugins/superstacks/skills/test-driven-development .claude/skills/test-driven-developmentInstall the test-driven-development skill in Codex
~/.agents/skills/test-driven-development/SKILL.md
$ npx degit KunanonJ/superstacks/plugins/superstacks/skills/test-driven-development ~/.agents/skills/test-driven-developmentInstall the test-driven-development skill in Gemini CLI
~/.gemini/skills/test-driven-development/SKILL.md
$ npx degit KunanonJ/superstacks/plugins/superstacks/skills/test-driven-development ~/.gemini/skills/test-driven-developmentInstall the test-driven-development skill in Claude.ai
npx degit KunanonJ/superstacks/plugins/superstacks/skills/test-driven-development test-driven-development && zip -r test-driven-development.zip test-driven-development # claude.ai → Customize → Skills → + → Create skill → Upload a skill → test-driven-development.zip
Automated checks
Ran Nov 16, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablekunanonj/superstacks/plugins/superstacks/skills/test-driven-development is public and reachablegithub.com/kunanonj/superstacks/tree/HEAD/plugins/superstack ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-10-29github.com/kunanonj/superstacks/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/kunanonj/superstacks/blob/HEAD/plugins/superstack ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/kunanonj/superstacks/blob/HEAD/plugins/superstack ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 332 linesgithub.com/kunanonj/superstacks/blob/HEAD/plugins/superstack ↗Pass
SKILL.md
View on GitHubTest-Driven Development (TDD)
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.
When to Use
Always:
- New features
- Bug fixes
- Refactoring
- Behavior changes
Exceptions (ask your human partner):
- Throwaway prototypes
- Generated code
- Configuration files
Thinking "skip TDD just this once"? Stop. That's rationalization.
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
digraph tdd_cycle {
rankdir=LR;
red [label="RED\nWrite failing test", shape=box, style=filled, fillcolor="#ffcccc"];
verify_red [label="Verify fails\ncorrectly", shape=diamond];
green [label="GREEN\nMinimal code", shape=box, style=filled, fillcolor="#ccffcc"];
verify_green [label="Verify passes\nAll green", shape=diamond];
refactor [label="REFACTOR\nClean up", shape=box, style=filled, fillcolor="#ccccff"];
next [label="Next", shape=ellipse];
red -> verify_red;
verify_red -> green [label="yes"];
verify_red -> red [label="wrong\nfailure"];
green -> verify_green;
verify_green -> refactor [label="yes"];
verify_green -> green [label="no"];
refactor -> verify_green [label="stay\ngreen"];
verify_green -> next;
next -> red;
}
RED - Write Failing Test
Write one minimal test showing what should happen.
const result = await retryOperation(operation);
expect(result).toBe('success'); expect(attempts).toBe(3); });
Clear name, tests real behavior, one thing
</Good>
<Bad>
```typescript
test('retry works', async () => {
const mock = jest.fn()
.mockRejectedValueOnce(new Error())
.mockRejectedValueOnce(new Error())
.mockResolvedValueOnce('success');
await retryOperation(mock);
expect(mock).toHaveBeenCalledTimes(3);
});
Vague name, tests mock not code
Requirements:
- One behavior
- Clear name
- Real code (no mocks unless unavoidable)
Verify RED - Watch It Fail
MANDATORY. Never skip.
npm test path/to/test.test.ts
Confirm:
- Test fails (not errors)
- Failure message is expected
- Fails because feature missing (not typos)
Test passes? You're testing existing behavior. Fix test.
Test errors? Fix error, re-run until it fails correctly.
GREEN - Minimal Code
Write simplest code to pass the test.
Don't add features, refactor other code, or "improve" beyond the test.
Verify GREEN - Watch It Pass
MANDATORY.
npm test path/to/test.test.ts
Confirm:
- Test passes
- Other tests still pass
- Output pristine (no errors, warnings)
Test fails? Fix code, not test.
Other tests fail? Fix now.
"Other tests" means the project's suite, not just your file. A
green run of the test you wrote is not a green suite. Before you call
the change done, run the project's test command (bare pytest,
npm test, cargo test — whatever the repo uses) even when your task
named only one test file. A scope statement in your task bounds the
deliverable, not your verification. Any failure that run shows —
including one you didn't cause — goes in your report by name; a red
test you watched scroll past and didn't mention is a report falsified
by omission.
REFACTOR - Clean Up
After green only:
- Remove duplication
- Improve names
- Extract helpers
Keep tests green. Don't add behavior.
Repeat
Next failing test for next feature.
Good Tests
| Quality | Good | Bad |
|---|---|---|
| Minimal | One thing. "and" in name? Split it. | test('validates email and domain and whitespace') |
| Clear | Name describes behavior | test('test1') |
| Shows intent | Demonstrates desired API | Obscures what code should do |
When writing or changing any test, read writing-good-tests.md for the rules that keep tests honest:
- Name the production change that would make the test fail — before writing it
- Assert on real behavior, never on mock behavior
- Keep test-only code in test utilities, out of production classes
- Understand a dependency's side effects before mocking it
Common Rationalizations
| Excuse | Reality |
|---|---|
| "Too simple to test" | Simple code breaks. Test takes 30 seconds. |
| "I'll test after" | Tests written after pass immediately — which proves nothing. They may test the wrong thing, test the implementation instead of the behavior, or miss the edge case you forgot. You never watched it fail, so you never proved it can catch the bug. Test-first forces that failure. |
| "Tests after achieve same goals (spirit not ritual)" | Tests-after answer "what does this do?"; tests-first answer "what should this do?" Tests written after are biased by the code you already wrote — you verify the cases you remembered, not the ones you'd have discovered. Coverage without proof the tests work. |
| "Already manually tested" | Manual testing is ad-hoc: no record of what you covered, no way to re-run it when the code changes, easy to forget cases under pressure. "Worked when I tried it" ≠ comprehensive. Automated tests run the same way every time. |
| "Deleting X hours is wasteful" | Sunk cost fallacy — that time is already spent either way. The real choice: rewrite with TDD (high confidence) vs. keep it and bolt tests on after (low confidence, likely bugs). Keeping code you can't trust is the waste. |
| "Keep as reference, write tests first" | You'll adapt it. That's testing after. Delete means delete. |
| "Need to explore first" | Fine. Throw away exploration, start with TDD. |
| "Test hard = design unclear" | Listen to test. Hard to test = hard to use. |
| "TDD will slow me down" | TDD IS the pragmatic path: catches bugs before commit, prevents regressions, lets you refactor without fear. "Pragmatic" shortcuts mean debugging in production — slower, not faster. |
| "Manual test faster" | Manual doesn't prove edge cases. You'll re-test every change. |
| "Existing code has no tests" | You're improving it. Add tests for existing code. |
Red Flags - STOP and Start Over
- Code before test
- Test after implementation
- Test passes immediately
- Can't explain why test failed
- Tests added "later"
- Rationalizing "just this once"
- "I already manually tested it"
- "Tests after achieve the same purpose"
- "It's about spirit not ritual"
- "Keep as reference" or "adapt existing code"
- "Already spent X hours, deleting is wasteful"
- "TDD is dogmatic, I'm being pragmatic"
- "This is different because..."
All of these mean: Delete code. Start over with TDD.
Example: Bug Fix
Bug: Empty email accepted
RED
test('rejects empty email', async () => {
const result = await submitForm({ email: '' });
expect(result.error).toBe('Email required');
});
Verify RED
$ npm test
FAIL: expected 'Email required', got undefined
GREEN
function submitForm(data: FormData) {
if (!data.email?.trim()) {
return { error: 'Email required' };
}
// ...
}
Verify GREEN
$ npm test
PASS
REFACTOR Extract validation for multiple fields if needed.
Verification Checklist
Before marking work complete:
- Every new function/method has a test
- Watched each test fail before implementing
- Each test failed for expected reason (feature missing, not typo)
- Wrote minimal code to pass each test
- All tests pass
- Output pristine (no errors, warnings)
- Tests use real code (mocks only if unavoidable)
- Edge cases and errors covered
Can't check all boxes? You skipped TDD. Start over.
When Stuck
| Problem | Solution |
|---|---|
| Don't know how to test | Write wished-for API. Write assertion first. Ask your human partner. |
| Test too complicated | Design too complicated. Simplify interface. |
| Must mock everything | Code too coupled. Use dependency injection. |
| Test setup huge | Extract helpers. Still complex? Simplify design. |
Debugging Integration
Bug found? Write failing test reproducing it. Follow TDD cycle. Test proves fix and prevents regression.
Never fix bugs without a test.
Final Rule
Production code → test exists and failed first
Otherwise → not TDD
No exceptions without your human partner's permission.
Files in this skill
2test-driven-development skill questions
How do I install the test-driven-development skill in Claude Code?
Run npx degit KunanonJ/superstacks/plugins/superstacks/skills/test-driven-development ~/.claude/skills/test-driven-development. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the test-driven-development skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What is the core principle of TDD?
The core principle is to write the test first and watch it fail before writing any minimal code to make it pass.
What should I do if I wrote code before writing the test?
You must delete the code and start over from the tests.
What are the stages of the TDD cycle?
The cycle consists of RED (write a failing test), GREEN (write minimal code to pass), and REFACTOR (clean up the code).