harness-tdd
Skill48 starsChanged 6 months agoApache-2.0View on GitHub
Vertical-slice test-driven workflow for backend harness features and bug fixes. Use when adding or changing service, server, worker, contract, or repo-tool behavior, or when the user asks for TDD, red-green-refactor, or test-first implementation.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- lordm00n/skillstheir own version, first seen Oct 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- lordm00n/skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- backend-engineeringSkill
- contract-agentSkill
- harness-architecture-reviewSkill
- harness-diagnoseSkill
- harness-grillSkill
- harness-zoom-outSkill
- plannerSkill
- platform-ops-agentSkill
- server-agentSkill
- service-agentSkill
- skill-authoringSkill
- worker-agentSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 12 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use this skill to add or change behavior one vertical slice at a time.
- Distinctive: line 19
Prefer tests that survive internal refactors:
- Distinctive: line 32
Write one failing test at the correct public seam.
- Distinctive: line 33
Run it and confirm RED.
- Distinctive: line 34
Write the smallest correct code to pass.
- Distinctive: line 35
Run it and confirm GREEN.
- Distinctive: line 37
Run relevant path-scoped gates.
- Distinctive: line 41
Do not write all tests first and then all implementation.
- Distinctive: line 42
Do not test private helpers when a public seam can express the behavior.
- Distinctive: line 43
Do not mock internal collaborators you own.
- Distinctive: line 44
Do not add speculative behavior for future tests.
- Distinctive: line 45
Do not expose internal seams only for test convenience.
- Very specific: line 53
After GREEN, look for shallow modules, duplicated rules, primitive obsession, hidden coupling, or oversized traits.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Harness TDD
Use this skill to add or change behavior one vertical slice at a time.
Workflow skills guide process. Ownership skills still decide writable boundaries.
Philosophy
Tests should verify observable behavior through public seams, not implementation details.
Prefer tests that survive internal refactors:
- service public API or application seam
- BFF handler or HTTP route behavior
- worker replay, checkpoint, or projection seam
- contract compatibility or drift seam
- repo-tool CLI or validator seam
Loop
For each behavior:
- Pick one observable behavior.
- Write one failing test at the correct public seam.
- Run it and confirm RED.
- Write the smallest correct code to pass.
- Run it and confirm GREEN.
- Refactor only while GREEN.
- Run relevant path-scoped gates.
Anti-Patterns
- Do not write all tests first and then all implementation.
- Do not test private helpers when a public seam can express the behavior.
- Do not mock internal collaborators you own.
- Do not add speculative behavior for future tests.
- Do not expose internal seams only for test convenience.
Mocking Rule
Mock true externals and hard runtime boundaries. Prefer local substitutes or in-memory adapters for owned seams when they provide better behavioral evidence.
Refactor Check
After GREEN, look for shallow modules, duplicated rules, primitive obsession, hidden coupling, or oversized traits. If the fix reveals architecture friction, hand off to harness-architecture-review.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

