Individual skill
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
skills/_canonical/process/test-driven-development/SKILL.md
Source commit 344815052870e4b1be2486350ba52a8d1c6afeb2
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 8,722
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-harness Repository topic
- agent-orchestration Repository topic
- agent-skills Repository topic
- ai-coding Repository topic
- claude-code Repository topic
- cli Repository topic
- codex-cli Repository topic
- multi-agent Repository topic
- tmux Repository topic
- typescript Repository topic
- writing Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
LICENSE.txtdoc · 1,070 bytesSKILL.mdcore · 12,641 bytesSKILL.mdcore · 12,641 bytesSKILL.mdcore · 12,641 bytesSKILL.mdcore · 12,641 bytesSKILL.mdcore · 12,641 bytestesting-anti-patterns.mddoc · 8,251 bytes
Read excerpt
# Test-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.
**A strong default in service of shipping — not a law that outranks it.** TDD earns its keep where a failing test pins down behavior you'd otherwise get wrong: core logic, contracts, tricky edge cases. Match it to stakes — reach for it where test-first genuinely de-risks the change; throwaway prototypes, one-line copy tweaks, and obvious glue don't need the ceremony. Don't dodge it with synonyms; equally, don't let it block you from shipping the working thing.
## When to Use
**Use test-first for selected behavior where regression risk warrants it:**
- New features