dev-style-tdd

Guide teams through end-to-end TDD cycles with red-green-refactor workflows.

Updated Jun 17, 2025

Search Tags:#testing #tdd #refactor #integration-testing #behavior #software-engineering

Ready to run

npx skills add https://github.com/nikbrunner/dots --skill dev-style-tdd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-style-tdd
Source: https://github.com/nikbrunner/dots/tree/main/common/.agents/skills/dev-style-tdd
Command: npx skills add https://github.com/nikbrunner/dots --skill dev-style-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development guides teams to express intended behavior through public interfaces, reducing rework and brittle refactors.

Core Features & Use Cases

Integrates red-green-refactor workflow to drive incremental feature work and bug fixes.
Emphasizes integration-style tests that exercise public interfaces over internal implementations.
Supports test-first development and disciplined refactoring across projects.

Quick Start

Run a tracer-bullet cycle: write one failing test, implement the minimal code to pass, then refactor while preserving behavior.

Frequently Asked Questions about dev-style-tdd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is the red-green-refactor cycle in test-driven development?▼

The red-green-refactor cycle in test-driven development is an iterative process where you write a failing test, implement the minimal code to pass it, and then refactor while preserving behavior to reduce rework and brittleness.

How do I execute a tracer bullet cycle for feature development?▼

To execute a tracer bullet cycle for feature development, write one failing integration test that exercises a public interface, implement the minimal code required to pass it, and then refactor the implementation iteratively.

Should I write integration tests for public interfaces or internal implementations?▼

You should write integration tests for public interfaces rather than internal implementations to express intended behavior and ensure observable outcomes, which reduces brittle refactors during test-driven development.

Does test-driven development work for both feature development and bug fixes?▼

Test-driven development works for both feature development and bug fixes by guiding teams to express intended behavior through public interfaces using incremental vertical slices and disciplined refactoring.

Why does emphasizing implementation details cause brittle refactors?▼

Emphasizing implementation details causes brittle refactors because tests become tightly coupled to internal code structures rather than observable outcomes, increasing rework when the underlying implementation changes.

Can I apply test-driven development to any software project without specific testing frameworks?▼

You can apply test-driven development to any software project without specific framework dependencies, as the process focuses on expressing behavior through public interfaces using vertical slices and integration tests.