Tdd

Build behavior test-first using thin vertical slices and explicit red-green-refactor loops. Use when the user requests TDD or when a stable observable contract should drive implementation.From its SKILL.md

Install

npx -y skills add kevinb361/agent-skills --skill tdd

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.0 KB, 163 tokens by cl100k_base, as published. Nobody here has run it

Test-driven development

Work in vertical behavior slices rather than building all tests, then all internals.

For each slice:

State one observable behavior and boundary.
Add the smallest test that expresses it through a stable public surface.
Run the focused test and confirm it fails for the intended reason.
Implement the minimum coherent behavior.
Run the focused test and relevant nearby tests.
Refactor only while green.
Repeat with the next behavior, edge case, or failure path.

Do not write tests that merely mirror implementation details. Do not weaken assertions to obtain green. If the test passes before implementation, determine whether the behavior already exists or the test is ineffective.

At completion, run the project's canonical gate and report both the initial red evidence and final verification.