the-own-lab/tdd
skills/tdd/SKILL.md
Test-driven development cycle: RED → GREEN → REFACTOR. Every code change goes through it, including /debug regression tests.
development
Updated Apr 22, 2026
$ install --global
skillsauthnpx skillsauth add the-own-lab/Claude-company-of-one tddInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 11:17 AM129.1s1 file scanned
SKILL.md
- name:
- tdd
- description:
- Test-driven development cycle: RED → GREEN → REFACTOR. Every code change goes through it, including /debug regression tests.
tdd
Purpose
Default execution loop for any code change in /dev and /debug. RED → GREEN →
REFACTOR, one behavior at a time. Produces tests that actually describe behavior
rather than lock in an implementation.
Inputs
BRIEF.md## Current Contract(what needs to work) and, for/dev, thetest-planoutput (what to cover).- For
/debug,### Root Causefromdebug-validate— the regression test exercises the exact reproduction.
Outputs
- New test file(s) added / modified, each corresponding to one behavior.
tdddoes not commit by itself; command/repo policy decides whether the Main Agent commits after docs update. - Production code delivering the minimum to make each new test pass.
- Refactored code after green, tests still passing.
Procedure
RED
- Write a test for ONE behavior. Name it
should X when Y. - Use Arrange-Act-Assert layout.
- Run it. Watch it fail. Confirm the failure message names the missing behavior, not a syntax error.
GREEN
- Write the minimum code to make that test pass. No generalization, no unrelated cleanup.
- Run the test. It passes.
REFACTOR
- Improve names, remove duplication, simplify. Do NOT add new behavior.
- Run tests after each edit. Keep the bar green.
Repeat until the test plan (or, for /debug, the regression test) is complete.
Failure modes
- Code written before the test → delete the code, write the test first. No exceptions.
- Test passes on the first run (skipped RED) → the test is not exercising the change; rewrite it to fail first.
- Test name contains
and→ split into two tests. - More than ~10 tests for one feature → feature is too big; route back to
spec-writing.
Does not do
- Does not decide which tests to write (that is
test-plan). - Does not run the final verification sweep (that is
verify). - Does not mock internal logic; mock only external services.
Related Skills
the-own-lab/write-brief
documentation
VerifiedTrustedCommunity
Update BRIEF.md sections during a command run. Any skill that produces a brief-persisted artifact calls this to write it back.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/verify
development
VerifiedTrustedCommunity
Post-code check: run tests + confirm TODO acceptance items map to passing tests; applies a security lens but is not a separate scan.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/update-docs
documentation
VerifiedTrustedCommunity
Command post-step: write CHANGELOG + TODO once per command run. One call, not per-skill doc writes.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/spec-writing
content-media
VerifiedTrustedCommunity
Author REQUIREMENTS.md + DESIGN.md + TODO.md for a feature. The three files are one contract; they ship together.
SKILL.mdUpdated Apr 22, 2026