From sdd
Enforce Red-Green-Refactor TDD cycle. Use when implementing any new class or method — write the failing test first, then make it pass. Never write production code before a failing test exists.
npx claudepluginhub tstapler/dotfiles --plugin sddThis skill uses the workspace's default tool permissions.
**No production code without a failing test first.**
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
No production code without a failing test first.
If you have written production code before a failing test:
There are no exceptions. "This is too simple to need a test first" is rationalisation.
Write the smallest amount of production code that makes the test pass. Do not add logic that isn't required by a failing test.
Clean the code while keeping tests green:
For each public method, write at minimum:
| Thought | Reality |
|---|---|
| "This is too simple to need a test" | Simple code breaks too. Write the test. |
| "I'll write tests after to save time" | You won't. The test discovers design flaws. |
| "The test would just mirror the implementation" | Then the implementation is too tightly coupled. |
| "Integration tests cover this" | Unit tests run in milliseconds. Write both. |