Develops software via a TDD cycle of Red-Green-Refactor with behavior-focused tests.
npx skills add https://github.com/mpsuesser/workspace --skill tdd-mpsuesser
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/mpsuesser/workspace/tree/main/dotconfig/pi/agent/skills/.deprecated/tdd Command: npx skills add https://github.com/mpsuesser/workspace --skill tdd-mpsuesser
This Skill helps you avoid fragile, implementation-coupled tests by applying a disciplined test-driven development loop that keeps tests focused on user-visible behavior.
Use this when you want to build new features or fix bugs by designing behavior-driven tests, especially when you care about integration tests and maintaining test stability through refactors.
Apply the TDD red-green-refactor loop to implement one public behavior at a time, using integration-style tests and mocking only system boundaries.
High-intent search queries and answers about installing and using this skill.
Integration tests survive refactoring by asserting behavior through public interfaces only and mocking external collaborators exclusively at system boundaries like APIs, databases, and filesystems to avoid implementation coupling.
The red-green-refactor workflow in test-driven development involves writing a failing test for one behavior, writing minimal code to pass it, and then safely refactoring to remove duplication while maintaining test coverage.
Vertical slicing in feature development moves one behavior at a time through the test-driven development loop, acting as tracer bullets to incrementally verify user-visible behavior rather than bulk-writing tests first.
Unit tests break during refactoring when they are implementation-coupled rather than behavior-focused, which is resolved by applying test-driven development to write integration-style checks using public-interface-only assertions.
Mocking in test-driven development should be restricted to system boundaries such as external APIs, databases, time, randomness, and the filesystem to keep tests meaningful and focused on user-visible behavior.
Refactor candidates in TDD should be identified after the test passes during the refactor phase, allowing you to safely remove duplication and shallow modules while ensuring behavior stays covered.
qdzshAutomates red-green-refactor cycles for vertical slices with failing tests first.
Ilenburg1993Consolidate Audit Agent and Diagnostic Agent systems into shared modules with SQLite persistence.
linenoizeWrite failing tests before implementation using red-green TDD workflows.
javierhbrGenerate failing executable tests from natural language acceptance criteria.
