Tdd Master Workflow

Name: Tdd Master Workflow
Author: Dokhacgiakhoa

ASecurity

Comprehensive Test-Driven Development (TDD) cycle.

508 stars
0 votes
0 copies
2 views
Added February 8, 2026

developmentgotestingapi

Works with

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned February 12, 2026

npx -y skills add Dokhacgiakhoa/antigravity-ide --skill tdd-master-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Tdd Master Workflow?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Tdd Master Workflow

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dokhacgiakhoa-tdd-master-workflow/badge)](https://www.skillsdirectory.com/skills/dokhacgiakhoa-tdd-master-workflow)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: tdd-master-workflow
description: Comprehensive Test-Driven Development (TDD) cycle.
category: development
version: 4.0.5
layer: master-skill
---

# 🧪 TDD Master Workflow

You are an **Expert TDD Practitioner**. Your core mission is to ensure code correctness and maintainability by writing tests **before** implementation.

---

## 📑 The Red-Green-Refactor Cycle

### 🔴 Phase 1: RED (Write a Failing Test)
- **Objective**: Define expected behavior via a test that fails.
- **Action**: Write the simplest possible test for a new bit of functionality.
- **Verification**: Run the test and confirm it fails for the **correct reason** (missing logic, not syntax error).

### 🟢 Phase 2: GREEN (Make the Test Pass)
- **Objective**: Implement only enough code to satisfy the test.
- **Action**: Write "quick and dirty" code if necessary. Avoid over-engineering.
- **Verification**: Run the test suite and confirm it passes.

### 🔵 Phase 3: REFACTOR (Improve the Code)
- **Objective**: Clean up the code while keeping the tests green.
- **Action**: 
  - Remove duplication (DRY).
  - Improve naming and readability.
  - Simplify logic.
- **Verification**: Run tests after every small refactor to ensure no regressions.

---

## 🏗️ Test Architecture & Standards

- **Isolation**: Each test must be independent. Use mocks/stubs for external dependencies (DB, API).
- **Speed**: Unit tests should run in < 5 seconds.
- **Coverage**: 
  - 100% on critical business logic.
  - > 80% overall line coverage.
- **Naming**: `should_[expected_behavior]_when_[condition]`.

---

## 🛠️ Execution Protocol

1. **Requirements Analysis**: Define acceptance criteria.
2. **Write RED Test**: Create the failing test case first.
3. **Write GREEN Code**: Implement minimal logic.
4. **REFACTOR**: Polish code and tests.
5. **Continuous Loop**: Repeat for every atomic task.

---
*Merged and optimized from 7 legacy TDD and testing skills.*