tdd

Implement test-driven development workflows with vertical slicing and behavior-focused tests.

28|3|Updated Apr 28, 2026

Search Tags:#testing #tdd #refactoring #best-practices #software-design

Ready to run

npx skills add https://github.com/Minara-AI/cc-connect --skill tdd-minara-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/Minara-AI/cc-connect/tree/main/.claude/skills/tdd
Command: npx skills add https://github.com/Minara-AI/cc-connect --skill tdd-minara-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the common pitfalls of test-driven development, such as horizontal slicing and implementation-coupled testing, by enforcing a vertical, behavior-driven workflow.

Core Features & Use Cases

Vertical Slicing: Guides the user through tracer-bullet development where each test corresponds to a single, minimal implementation step.
Interface-First Design: Provides clear guidelines on designing deep modules and testable interfaces that survive refactoring.
Mocking Strategy: Defines strict boundaries for when to use mocks, ensuring tests verify observable behavior rather than internal implementation details.

Quick Start

Activate the tdd skill and ask it to help you plan a vertical slice for the current feature by identifying the first behavior to test.

Frequently Asked Questions about tdd

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

FAQPage Schema

What is vertical slicing in test-driven development?▼

Mocking should be used strictly at module boundaries to verify observable behavior rather than internal implementation details. This disciplined mocking strategy ensures tests remain robust and survive future refactoring.

How do I write behavior-focused tests for robust code?▼

To write behavior-focused tests, design deep modules with testable interfaces first, then apply a vertical slicing workflow. This verifies the public API and ensures tests validate observable behavior rather than implementation coupling.

Does test-driven development work for refactoring existing software?▼

Test-driven development supports refactoring by prioritizing public API verification and decoupling tests from implementation details. Designing deep modules with testable interfaces ensures your test suite survives structural code changes.

What's the best way to avoid implementation-coupled testing?▼

The best way to avoid implementation-coupled testing is enforcing a vertical, behavior-driven workflow with strict mocking boundaries. This approach prioritizes interface-first design and validates observable behavior over internal code structure.

How do I plan a vertical slice for a new software feature?▼

Plan a vertical slice by identifying the first behavior to test, then applying the red-green-refactor loop. This tracer-bullet development approach guides you through minimal implementation steps mapped to individual behavior tests.