tdd

Guide test-driven development cycles with vertical-slice tracer bullets.

5|Updated Apr 24, 2026

Search Tags:#workflow #testing #tdd #refactor #test-driven-development #vertical-slices #public-interfaces

Ready to run

npx skills add https://github.com/timurgaleev/vibestack --skill tdd-timurgaleev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/timurgaleev/vibestack/tree/main/skills/tdd
Command: npx skills add https://github.com/timurgaleev/vibestack --skill tdd-timurgaleev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development with the red-green-refactor loop. Vertical-slice tracer bullets, not horizontal slicing. Tests verify behavior through public interfaces, not implementation details, so they survive refactors. Sub-docs cover deep modules, interface design, mocking, refactoring, and what makes a good test.

Core Features & Use Cases

Vertical-slice workflows guide end-to-end cycles from planning to refactor.
Tests focus on observable behavior via public interfaces to survive refactors.
Sub-docs provide deep modules, interface design, mocking, and refactoring guidelines.

Quick Start

Write one tracer bullet test against a public interface and implement the minimal code needed 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 test-driven development cycles for reliable code?▼

Enforce test-driven development by applying the red-green-refactor loop with vertical-slice tracer bullets that validate behavior through public interfaces, ensuring tests survive refactoring. This disciplined workflow guides end-to-end cycles from planning through implementation to refactoring.

What is vertical-slice testing in TDD workflows?▼

Vertical-slice testing in TDD workflows means writing end-to-end tracer bullets that validate behavior through public interfaces rather than testing implementation details horizontally, ensuring tests remain durable and survive refactoring. This approach validates complete feature paths.

How do I write tests that survive refactoring?▼

Write tests that survive refactoring by verifying observable behavior through public interfaces rather than implementation details, following structured TDD workflow documentation that emphasizes deep modules and interface design. This ensures tests remain valid across code changes.

Do I need mocking guidelines for test-driven development?▼

Mocking guidelines for test-driven development are included as sub-documents covering deep modules, interface design, mocking, and refactoring practices. These guidelines help structure tests around public interfaces while maintaining disciplined TDD cycles.

What's the best way to start a TDD cycle for feature development?▼

Start a TDD cycle for feature development by writing one tracer bullet test against a public interface and implementing the minimal code needed to pass, following vertical-slice workflows from planning through refactor. This establishes end-to-end behavior validation early.

When should I not use vertical-slice testing?▼

Vertical-slice testing may not suit projects where end-to-end public interfaces are undefined or when horizontal layer testing is specifically required for isolated component validation. The approach emphasizes behavioral validation through complete feature paths rather than unit-level isolation.