One-click install
npx skills add https://github.com/Insik-Han/han-monorepo-template --skill tdd-insik-han
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/Insik-Han/han-monorepo-template/tree/main/.agents/skills/tdd
Command: npx skills add https://github.com/Insik-Han/han-monorepo-template --skill tdd-insik-han

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD helps teams deliver features with confidence by driving design through tests before implementation, reducing regressions and guiding refactoring.

Core Features & Use Cases

  • Red-Green-Refactor workflow with incremental feature development.
  • Integration-style tests that exercise public interfaces rather than internals.
  • Clear guidance for vertical slicing and safe refactoring across modules.

Quick Start

Plan the first tracer bullet by writing a single failing test for the desired behavior and implement the minimal code to pass it.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I start test-driven development for a new feature?

Start test-driven development by writing a single failing integration test for the desired behavior, then implement the minimal code required to pass it. This red-green-refactor cycle drives incremental feature development safely.

What is the red-green-refactor cycle in software testing?

The red-green-refactor cycle in software testing is a discipline of writing a failing test, implementing minimal code to pass it, and then refactoring safely. It drives design through tests before implementation to reduce regressions.

Does test-driven development work for incremental refactoring across existing modules?

Yes, test-driven development supports incremental refactoring across existing modules by relying on integration-style tests. These tests exercise public interfaces rather than internal implementation details to ensure safe modifications.

How do I use vertical slicing with integration testing in TDD?

Use vertical slicing with integration testing by building features incrementally through public interfaces. Plan a tracer bullet, write a failing test for the desired behavior, and implement the minimal code to pass it across the stack.

When should I not use test-driven development for bug fixes?

Avoid test-driven development for bug fixes or refactoring when the codebase lacks dependency-injection-friendly design or public interfaces. Without integration-style tests exercising external behavior, the red-green-refactor workflow cannot guarantee safe changes.

What's the best way to drive feature implementation with confidence using TDD?

The best way to drive feature implementation with confidence using TDD is adopting the red-green-refactor discipline. Write failing integration tests first to guide dependency-injection-friendly design and ensure incremental refactors reduce regressions.