Guide test-driven development through the red-green-refactor loop.
npx skills add https://github.com/AcendWay/ai-skills-library --skill tdd-acendway
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/AcendWay/ai-skills-library/tree/main/skill-folders/tdd Command: npx skills add https://github.com/AcendWay/ai-skills-library --skill tdd-acendway
TDD helps you build or fix software with confidence by forcing tests to validate real, user-facing behavior instead of brittle implementation details.
Ask the AI to design a red-green-refactor TDD plan for your next feature or bugfix, focusing on the public interface behaviors you want to prove first.
High-intent search queries and answers about installing and using this skill.
Red-green-refactor TDD works by writing a failing test for a desired behavior, implementing the minimum code to pass it, and then refactoring safely. It forces tests to validate real public interface behavior instead of brittle implementation details.
The best way to write integration tests that survive refactoring is to exercise the public interface and real code paths. This behavior-first approach ensures tests verify vertical-slice functionality end-to-end without breaking during implementation changes.
To plan test design for a new feature using TDD, prioritize which behaviors matter most and design public interfaces that make testing natural. This behavior-first planning guides the red-green-refactor loop to produce reliable, tracer-bullet tests.
Yes, you can use TDD for fixing bugs with integration-style verification. The red-green-refactor loop applies to bugfixes by writing a failing test that reproduces the bug, implementing the fix to reach green, and refactoring without breaking existing tests.
Tests break when refactoring code because they likely validate brittle implementation details instead of real user-facing behavior. TDD solves this by using integration-style verification that exercises the public interface, producing tests that survive refactors.
You should not use test-driven development for tasks lacking a clear public interface or behavior to verify. TDD requires planning interface behaviors and writing tracer-bullet tests, making it suited for features and bugfixes needing integration-style verification rather than pure structural changes.
polikeijiWrite and maintain Markdown product specification documents with frontmatter versioning.
franroaEnforce test-first development with failing tests before production code.
gilesknapApply test-driven development with red-green-refactor cycles for features and bug fixes.
GaryOcean428Enforce Test-Driven Development by mandating failing tests before implementation code.
