tdd

Enforce red-green-refactor cycles with public-interface tests across languages.

3|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/ralvarezdev/ralvaskills --skill tdd-ralvarezdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/ralvarezdev/ralvaskills/tree/main/skills/workflows/tdd
Command: npx skills add https://github.com/ralvarezdev/ralvaskills --skill tdd-ralvarezdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development guidance that helps teams focus on behavior via red-green-refactor cycles, avoiding implementation-detail tests.

Core Features & Use Cases

  • Red-green-refactor workflow with public-interface testing
  • Tracer bullet technique to validate one behavior at a time
  • Vertical slicing approach to avoid brittle tests
  • Guidance for planning, refactoring, and maintaining test quality across languages

Quick Start

Outline one critical behavior and write a minimal end-to-end test that exercises the public API, then implement the smallest change to pass.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I enforce red-green-refactor cycles in test-driven development?

Test-driven development red-green-refactor cycles are enforced by automating workflows that guide teams through planning, writing minimal failing tests, implementing code to pass, and iterative refactoring while focusing on public interfaces.

How do I write tests for behavior without leaking implementation details?

Testing behavior without leaking implementation details is achieved by integrating tests exclusively via public interfaces, using vertical slices and the tracer bullet technique to validate one behavior at a time without creating brittle tests.

Can I apply TDD workflows across different programming languages like TypeScript, Go, and Python?

TDD workflows can be applied across TypeScript, Go, Python, or any language, providing language-agnostic guidance for feature development, bug fixes, planning, tracer bullets, and maintaining test quality across diverse software projects.

What's the best way to start TDD with vertical slices and public interfaces?

Starting TDD with vertical slices involves outlining one critical behavior and writing a minimal end-to-end test that exercises the public API, then implementing the smallest code change required to pass the test.

Why does my TDD workflow produce brittle tests tied to implementation details?

TDD workflows produce brittle tests when they leak implementation details instead of targeting behavior; adopting vertical slicing and public-interface testing prevents this by validating one behavior at a time through tracer bullets.

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

Test-driven development works for both feature development and bug fixes, automating disciplined workflows that enforce red-green-refactor cycles, guide tracer bullets, and maintain testability across software projects.