
Tdd Pack
- Updated July 30, 2026
- s-hiraoku/claude-harnesses
tdd-pack enforces Red-Green-Refactor test-driven development with subagent context isolation between phases. Developers use it to build features test-first, keeping each TDD phase clean and disciplined.
Key points
- Red-Green-Refactor loop
- Subagent context isolation per phase
- Disciplined test-first flow
Tdd Pack by the numbers
- Data as of Jul 31, 2026 (Skillselion catalog sync)
/plugin marketplace add s-hiraoku/claude-harnesses/plugin install tdd-pack@claude-harnessesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Last updated | July 30, 2026 |
|---|---|
| Repository | s-hiraoku/claude-harnesses ↗ |
What it does
Enforces Red-Green-Refactor TDD with subagent context isolation between phases for disciplined test-first development.
README.md
tdd-pack
Red-Green-Refactor TDD with strict context isolation between phases.
Components
- Skill:
tdd - Subagents:
tdd-test-writer,tdd-implementer,tdd-refactorer - Command:
/tdd
Install
claude /plugin install tdd-pack@claude-harnesses
Usage
/tdd add export support to the report module
Why isolation matters
LLMs that see both the spec and the implementation tend to write tests that match the implementation, not the intent. Isolating phases through separate subagents lets each phase focus on a single concern:
- The test writer sees the spec, never the implementation.
- The implementer sees the failing test, never the spec.
- The refactorer sees post-Green code, never the spec or test design notes.
This is honor-system enforcement (each subagent's prompt forbids reading certain inputs) — combine with permissions allowlists for stronger guarantees.