tdd

Guide users through red-green-refactor cycles for test-driven development.

26|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/TeamSloppy/Sloppy --skill tdd-teamsloppy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/TeamSloppy/Sloppy/tree/main/Sources/sloppy/Resources/Skills/tdd
Command: npx skills add https://github.com/TeamSloppy/Sloppy --skill tdd-teamsloppy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development (TDD) helps teams build robust software by writing tests before code, guiding design and reducing regressions.

Core Features & Use Cases

  • Emphasizes end-to-end, integration-style testing through public interfaces.
  • Encourages vertical slices (one test → one implementation) and incremental refactors.
  • Use case: when starting a feature, write a test that describes the desired behavior, implement only enough to pass, then iterate.

Quick Start

Identify a behavior, write a failing test for it, then implement the minimal code to pass.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I practice test-driven development using red-green-refactor cycles?

Test-driven development using red-green-refactor cycles involves writing a failing test for a specific behavior, implementing only enough code to pass it, then iteratively refactoring. This approach emphasizes vertical slices and incremental design improvements.

What is the best way to structure integration tests for TDD?

The best way to structure integration tests for TDD is through end-to-end, integration-style testing via public interfaces. This encourages vertical slices where one test maps to one implementation, ensuring robust software design.

How does writing tests before code improve software design?

Writing tests before code improves software design by guiding the architecture through desired behavior and reducing regressions. It enforces well-structured interfaces and iterative tracer-bullet cycles for robust software.

Do I need to write unit tests or integration tests for test-driven development?

For test-driven development, you should emphasize end-to-end, integration-style tests over isolated unit tests. Testing through public interfaces validates vertical slices and ensures the desired behavior works across the system.

When should I not use vertical slices in test-driven development?

You should not use vertical slices in test-driven development when a feature requires extensive cross-cutting concerns that cannot be validated through a single public interface, as the workflow relies on one test mapping directly to one implementation.