TDD Implement
Execute TDD implementation with a 3-agent team (QA, Implementor, Reviewer) following Red-Green-Review cycle. Use when Claude needs to (1) implement features using TDD methodology, (2) run a multi-agent team for code changes, (3) enforce minimal working code through test-driven development. Triggers on "tdd", "implement with tdd", "tdd team", "red green refactor", "tdd implement".
Install
npx skills add UserAd/ClaudeSkills --skill tdd-implementgit clone --depth 1 https://github.com/UserAd/ClaudeSkills.git /tmp/ClaudeSkills
mkdir -p ~/.claude/skills
cp -r /tmp/ClaudeSkills/skills/tdd-implement ~/.claude/skills/tdd-implementPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# TDD Team Implementation
## User Input
```text
$ARGUMENTS
```
Consider user input before proceeding (if not empty).
## Prerequisites
The lead shall read `.specify/memory/constitution.md` for project principles and constraints before starting.
The lead shall read spec/plan/tasks files for the current feature (if they exist).
The lead shall read `CLAUDE.md` for quality gates.
## Core Principles
Include in EVERY agent prompt. See [references/agent-rules.md](references/agent-rules.md) for full text.
Each agent shall write the smallest amount of code that satisfies requirements and tests.
Each agent shall prefer simple solutions over clever ones.
Each agent shall not add features, handling, or abstractions beyond requirements or tests.
Each agent shall not add docstrings, comments, type hints, or refactoring beyond what the task demands.
Each agent shall treat requirements as the maximum scope ceiling.
## Team
Create via TeamCreate, then spawn 3 agents:
| Role | Model | subagent_type |
|------|-------|---------------|
| qa | sonnet | general-purpose |
| implementor | sonnet | general-purpose |
| reviewer | opus | general-purpose |
## Workflow
```
RED → GREEN → QUALITY GATES → REVIEW → (REVISE loop, max 3) → DONE
```
### Phase 1: RED — Failing Tests
Assign to **qa**. Use prompt from [references/qa-prompt.md](references/qa-prompt.md).
The lead shall substitute `{REQUIREMENTS}` with requirements from user input or spec files.Details
- Skill name
tdd-implement- Repository
- UserAd/ClaudeSkills
- Path
skills/tdd-implement/SKILL.md- Repo updated
- 29 July 2026
FAQ
What does the TDD Implement skill do?
Execute TDD implementation with a 3-agent team (QA, Implementor, Reviewer) following Red-Green-Review cycle. Use when Claude needs to (1) implement features using TDD methodology, (2) run a multi-agent team for code changes, (3) enforce minimal working code through test-driven development. Triggers on "tdd", "implement with tdd", "tdd team", "red green refactor", "tdd implement".
How do I install the TDD Implement skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add UserAd/ClaudeSkills --skill tdd-implement. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is TDD Implement popular?
It lives in UserAd/ClaudeSkills, which has 8 GitHub stars and 0 forks.
Related skills
Architecture
8UserAd/ClaudeSkills
Manage architecture documentation in .architecture directory. Use when Claude needs to (1) create/update/delete architecture artifacts (domains, services, contracts, schemas), (2) validate architecture documentation, (3) query service dependencies or technology status, (4) document new services or domains, (5) work with RabbitMQ/Redis/PostgreSQL/ClickHouse/MongoDB/HTTP contracts. Triggers on "architecture", "add service", "add domain", "document service", "create contract", "validate architecture".
Codex Assistant
8UserAd/ClaudeSkills
Run AI-powered tasks using OpenAI Codex CLI. Use when Claude needs to (1) delegate code analysis or generation tasks to Codex, (2) get a second opinion on code changes, (3) perform parallel AI review, or (4) leverage Codex for specific tasks. Triggers on requests like "use codex to...", "run codex", "ask codex", "codex review".
Ears Translator
8UserAd/ClaudeSkills
Translate user stories and informal requirements into EARS (Easy Approach to Requirements Syntax) format. Use when Claude needs to (1) convert user stories to formal requirements, (2) transform informal requirements into structured EARS format, (3) review and improve existing requirements using EARS patterns, (4) create testable, unambiguous system requirements. Triggers on requests like "convert to EARS", "write requirements", "formalize these user stories", "EARS format".
Rpk Cluster
9redpanda-data/skills
Operate a Redpanda cluster from the CLI with the `rpk cluster` command group, and look up cluster commands and properties in the Redpanda docs. Use when checking cluster health or metadata, decommissioning or recommissioning brokers, getting, setting, importing, or resetting cluster config properties, balancing, moving, or recovering partitions, enabling maintenance mode, setting broker log levels, finalizing an upgrade, managing client quotas, running self-tests, restoring or mounting topics from Tiered Storage, or managing the Enterprise license and the cluster properties that turn on Enterp
Offer Clarity Diagnosis
9mardab96/landing-pages-claude-skills
Tests whether the offer on the page is specific enough to be believed and acted on, or whether it is a category description wearing an offer's clothes. Use when traffic and message match are fine but the page still does not convert.
Setup Pre Commit
5GAGAA-HUE/ASHUO-claude-skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.