tdd

Enforce test-first development with red-green-refactor cycles for pair programmers.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/ischung/go-sdlc-gan --skill tdd-ischung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/ischung/go-sdlc-gan/tree/main/tddskill/skill
Command: npx skills add https://github.com/ischung/go-sdlc-gan --skill tdd-ischung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD 수행 규칙 및 목표를 명확히 정의하고, 페어 프로그래머가 테스트를 먼저 작성하는 워크플로우를 실천하도록 돕습니다. 이 스킬은 Red-Green-Refactor 사이클의 규칙을 따른 작은 단위의 테스트 작성과 점진적 구현을 촉진합니다.

Core Features & Use Cases

  • 테스트 우선 개발: 구현보다 테스트를 먼저 작성하고, 한 번에 하나의 작은 단위를 완성합니다.
  • 안전한 반복 사이클: 실패를 확인하고, 최소 구현으로 그린 상태를 달성한 뒤 리팩토링합니다.
  • 협업 중심 워크플로우: 페어 프로그래밍의 원칙을 적용하여 팀의 품질과 속도를 높입니다.

Quick Start

Begin by writing one small failing test, then implement only the minimal code needed to pass it, and repeat in tiny steps.

Frequently Asked Questions about tdd

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

FAQPage Schema
How does test-driven development clarify software requirements before implementation?

Test-driven development clarifies requirements by forcing you to write a failing test that explicitly defines the expected behavior before any implementation code is written.

What is the best way to apply red-green-refactor cycles in pair programming?

The best way to apply red-green-refactor in pair programming is to write one small failing test, implement the minimal code to pass it, refactor safely, and repeat in tiny incremental steps.

Can I use this test-first development workflow for bug fixes and refactoring tasks?

Yes, you can use this test-first development workflow for bug fixes and refactoring tasks, as it targets software projects by ensuring incremental test cycles drive safe code modifications.

How do I start writing small-step tests for rapid software delivery?

To start writing small-step tests, begin by writing one small failing test, implement only the minimal code needed to pass it, and repeat the cycle to achieve rapid delivery.

Why should software testing workflows enforce explicit test naming conventions?

Software testing workflows enforce explicit test naming conventions to maintain clarity during incremental red-green-refactor cycles, ensuring every small-step test clearly communicates its specific requirement.