tdd-workflow

Guide development through Red-Green-Refactor cycles and Tidy First principles.

1|1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/datamaker-kr/synapse-claude-marketplace --skill tdd-workflow-datamaker-kr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/datamaker-kr/synapse-claude-marketplace/tree/main/plugins/platform-dev-team-common/skills/tdd-workflow
Command: npx skills add https://github.com/datamaker-kr/synapse-claude-marketplace --skill tdd-workflow-datamaker-kr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides developers in adopting and rigorously applying Test-Driven Development (TDD) and Kent Beck's Tidy First principles, ensuring robust and clean code.

Core Features & Use Cases

  • TDD Cycle Guidance: Provides step-by-step instructions for the Red-Green-Refactor cycle.
  • Tidy First Implementation: Helps separate structural and behavioral code changes for cleaner commits.
  • Commit Discipline: Enforces best practices for committing code only when tests pass and changes are logically sound.
  • Use Case: When starting a new feature, developers can consult this Skill to ensure they are writing failing tests first, implementing minimal code, and refactoring appropriately, all while keeping structural and behavioral changes separate.

Quick Start

Guide me through writing a failing test for a new user authentication feature.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I start writing tests using the TDD Red-Green-Refactor cycle?

TDD applies to bug fixing by first writing a failing test that reproduces the bug, then implementing the minimal code to fix it and pass the test, followed by refactoring to improve code quality while keeping tests green.

What are Tidy First principles for separating structural and behavioral changes?

Tidy First principles enforce separating structural changes, which alter code organization without changing behavior, from behavioral changes, ensuring logically sound and clean commits during software development.

When should I commit code when following a test-driven development workflow?

You should commit code only when tests pass and changes are logically sound. This Skill enforces commit discipline by requiring adherence to the Red-Green-Refactor cycle and separating structural and behavioral changes.

Can I use this TDD workflow guidance for both new feature implementation and refactoring?

Yes, this TDD workflow guidance applies to feature implementation, bug fixing, and refactoring workflows, requiring strict adherence to Red-Green-Refactor cycles and Tidy First principles for clean code.

Why separate structural and behavioral code changes during refactoring?

Separating structural changes from behavioral changes during refactoring keeps commits logically sound and maintains code quality. This discipline prevents unintended side effects and ensures tests consistently validate behavior.