test-driven-development · git:20261107.b65d54e · 2026-11-07 · sha256 545ee58b235f1b94
test-driven-development git:20261107.b65d54eA
Immutable. This exact content never changes and is served at /api/v1/blob/545ee58b235f1b94.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_elwxutznd44mwvkb/545ee58b235f1b94a48e92049fd1fd7aaf596fc3f80f1391c90af4e1aa687e03.json
Then /plugin install test-driven-development@markdownregistry-elwxutznd44mwvkb in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: test-driven-development description: Drive changes with Red→Green→Refactor; ensure behavior is verifiable and regression-safe. --- # Test-Driven Development ## When to Use - Adding or modifying core logic. - Fixing bugs and needing regression protection. - Requirements can be written as explicit input/output acceptance tests. ## Workflow 1. **Red**: Write a failing test describing the expected behavior. 2. **Green**: Write the minimal code to make the test pass. 3. **Refactor**: Clean up naming, structure, and duplication. 4. Repeat the cycle until acceptance criteria are met. ## Ironclad Rules - Do NOT write massive amounts of features before writing tests. - Focus on one small goal per cycle. - All tests MUST pass after refactoring.