tdd

Guide developers through a structured Test-Driven Development workflow for writing tests before code.

1|Updated Jun 9, 2026

Search Tags:#TDD #coding standards #test-driven development #software testing #developer best practices

Ready to run

npx skills add https://github.com/Marcus-Boni/chatbot-template --skill tdd-marcus-boni

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/Marcus-Boni/chatbot-template/tree/main/.claude/skills/tdd
Command: npx skills add https://github.com/Marcus-Boni/chatbot-template --skill tdd-marcus-boni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to Test-Driven Development (TDD), helping developers write tests before code, ensuring robust and maintainable software.

Core Features & Use Cases

Philosophy of TDD: Understand the core principles and best practices of TDD.
Good vs. Bad Tests: Learn to write effective tests that verify behavior through public interfaces.
Horizontal Slices vs. Vertical Slices: Discover the right approach to writing tests incrementally.
Workflow: Follow a structured workflow for planning, writing tests, and refactoring.
Checklist: Use the provided checklist to ensure tests are comprehensive and effective.

Quick Start

Use the tdd skill to learn how to write a test for a new feature in your project.

Frequently Asked Questions about tdd

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

FAQPage Schema

What is test-driven development and how does writing tests before code improve software quality?▼

Test-driven development is a coding practice where you write tests before implementation code to verify behavior through public interfaces. This approach ensures robust software by catching defects early and enforcing a structured workflow that enhances overall maintainability.

How do I start writing good tests and avoid common test-driven development anti-patterns?▼

To write good tests in test-driven development, verify behavior strictly through public interfaces and avoid common anti-patterns. Follow a structured workflow for planning, writing tests incrementally using horizontal or vertical slices, and refactoring to ensure comprehensive coverage.

What is the difference between horizontal and vertical slices in test-driven development?▼

In test-driven development, horizontal and vertical slices represent different approaches to writing tests incrementally. Understanding the right slice approach helps you build features progressively, ensuring tests remain effective and maintainable throughout the structured workflow.

Can I use test-driven development for maintaining existing codebases and improving developer best practices?▼

Yes, test-driven development is ideal for developers looking to improve code quality and maintainability in any project. By following the provided checklist and workflow, you can effectively apply these developer best practices to ensure tests remain comprehensive.

When should I not use test-driven development for software testing?▼

You should avoid test-driven development when writing tests that verify internal implementation details rather than public behavior, or when skipping the planning and refactoring workflow steps. These anti-patterns lead to brittle tests that reduce code maintainability instead of improving it.