dev-tdd

Implement software features using the Test-Driven Development methodology with a 6-gate execution process.

19|5|Updated Jan 4, 2026

Search Tags:#code quality #testing #tdd #development #refactoring #verification

Ready to run

npx skills add https://github.com/edwinhu/workflows --skill dev-tdd-edwinhu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-tdd
Source: https://github.com/edwinhu/workflows/tree/main/lib/skills/dev-tdd
Command: npx skills add https://github.com/edwinhu/workflows --skill dev-tdd-edwinhu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces the Test-Driven Development (TDD) methodology, ensuring that code is written to pass specific tests, leading to more robust and reliable software.

Core Features & Use Cases

TDD Cycle Enforcement: Guides the RED-GREEN-REFACTOR cycle, mandating failing tests before implementation.
Execution Gate Compliance: Ensures all necessary build, launch, and verification steps are completed before testing.
Use Case: When tasked with implementing a new user authentication module, this Skill will guide you to write failing tests for login, registration, and password reset scenarios before writing any actual code.

Quick Start

Follow the TDD cycle to implement the user login functionality by writing a failing test first.

Frequently Asked Questions about dev-tdd

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

FAQPage Schema

How do I enforce the Test-Driven Development cycle when implementing new software features?▼

Test-Driven Development is enforced by strictly following the RED-GREEN-REFACTOR cycle, which mandates writing a failing test first before any actual implementation code is written. This ensures code is built to pass specific tests.

What steps are required for TDD execution and log verification before end-to-end testing?▼

TDD execution requires passing a 6-gate process: build, launch with file-based logging, process checking, log reading, and log verification, completed strictly before any end-to-end testing or screenshots.

How do I document TDD cycles and refactoring learnings during development?▼

You document TDD cycles and refactoring learnings by adding entries to a LEARNINGS.md file. This is mandated during the Test-Driven Development process to track progress and record verification outcomes.

Why write failing tests for user authentication scenarios before writing the actual login code?▼

Writing failing tests for login, registration, and password reset scenarios first ensures the actual authentication code is written specifically to pass those tests, leading to more robust and reliable software.

Does Test-Driven Development require external dependencies or testing frameworks to start?▼

Test-Driven Development can be started without external dependencies, relying on internal references to guide the cycle. It requires a development environment supporting build, launch, and file-based logging for verification.

What is the best way to ensure code quality and verification during refactoring?▼

The best way to ensure code quality during refactoring is to enforce the TDD methodology with a strict 6-gate execution process and mandatory documentation in LEARNINGS.md, verifying logs before final testing.