IN PLAIN ENGLISH
What it does—and when it fits
Matt Pocock's TDD Skill treats implementation as a behavior-focused red → green loop: agree on public test seams, work in vertical slices, and use independent expected results. Refactoring is a separate review-stage activity, not part of that implementation loop. Tests should describe behavior that survives internal changes.
This is aimed at Engineers implementing behavior incrementally. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.
- Agree test seamsIdentify public boundaries before writing tests, including what each test catches and misses.
- Run vertical slicesWrite one failing behavior test, make the smallest change to pass it, then repeat.
- Refactor in reviewReview the diff and keep cleanup outside the red → green implementation loop.
- This profile is manually organized around the current upstream SKILL.md workflow.
- The capability boundary remains explicitly tied to mattpocock.
- Core uses, limitations, and risks are separated for pre-install review.
No verified review text is in the current dataset. Use the linked source for the latest discussion.
Read the source note ↗INSTALL BY AGENT
Choose your Agent
Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.
npx skills add https://github.com/mattpocock/skills --skill tdd --agent codexnpx skills add https://github.com/mattpocock/skills --skill tdd --agent codex -gProject install stays with this repository for team sharing. Personal install adds -g and works across repositories.
View install paths
.agents/skills/tdd/~/.agents/skills/tdd/Codex scans repository .agents/skills folders and the personal ~/.agents/skills directory. It normally detects newly added Skills automatically.
View path evidence ↗TYPICAL WORKFLOW
A practical workflow
Agree test seams
Identify public boundaries before writing tests, including what each test catches and misses.
Run vertical slices
Write one failing behavior test, make the smallest change to pass it, then repeat.
Refactor in review
Review the diff and keep cleanup outside the red → green implementation loop.
THE TRADEOFFS
Advantages and tradeoffs
Notable strengths
- This profile is manually organized around the current upstream SKILL.md workflow.
- The capability boundary remains explicitly tied to mattpocock.
- Core uses, limitations, and risks are separated for pre-install review.
Limitations
- The workflow needs a functioning test runner and clear public behavior.
- TDD cannot compensate for testing the wrong seam or misunderstanding the requirement.
BEST FIT
Who it is for
Engineers implementing behavior incrementally
Teams trying to make tests resilient to refactors
BEFORE YOU USE IT
Risks to review before use
False confidence
A green suite only validates the selected examples and seams. Keep exploratory, integration, and operational checks where needed.
Upstream instruction drift
Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.
SECURITY
What the permission profile means
- Declared access remains governed by the current upstream SKILL.md and runtime requests.
- Treat repository files, web content, and tool output as untrusted input.
- SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.
Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.
COMMON QUESTIONS
tdd Skill FAQ
What is the tdd Skill?
A practical test-driven development workflow for coding agents. Matt Pocock's TDD Skill treats implementation as a behavior-focused red → green loop: agree on public test seams, work in vertical slices, and use independent expected results. Refactoring is a separate review-stage activity, not part of that implementation loop. Tests should describe behavior that survives internal changes.
How do I install the tdd Skill?
Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the listed skills.sh page and upstream repository; verify the current SKILL.md.
Is the tdd Skill safe to use?
SkillSignal checked the source on 2026-09-23, but that is not a runtime test or security certification. Review the “False confidence” risk first and begin with the least access required.
INSIDE THE PACKAGE
Indexed files
TAGS
Manually expanded from the current upstream SKILL.md and linked source at mattpocock, checked 2026-08-19. This is an original summary, not an execution result or security certification.