tdd-workflow

Enforce a RED-GREEN-REFACTOR-VERIFY Test-Driven Development cycle for features and bug fixes.

21|3|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/JochenYang/Jochen-ai-rules --skill tdd-workflow-jochenyang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/JochenYang/Jochen-ai-rules/tree/main/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/JochenYang/Jochen-ai-rules --skill tdd-workflow-jochenyang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enforces a disciplined Test-Driven Development cycle to eliminate gaps in testing and reduce regression risk.

Core Features & Use Cases

  • Structured TDD cycle: Follow RED-GREEN-REFACTOR-VERIFY for every feature or bug fix to guide implementation.
  • Quality-first development: Prioritize failing tests, minimal implementation, and targeted refactoring for maintainability.
  • Team alignment: Integrates with development, review, and planning workflows to ensure consistent quality gates.

Quick Start

Create a failing test for a new feature, implement the minimal code to pass the test, refactor for clarity, and run the full test suite to verify coverage and regression protection.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce a strict test-driven development cycle for feature development?

To enforce a strict test-driven development cycle, you must follow the RED-GREEN-REFACTOR-VERIFY sequence: create failing tests first, implement minimal code to pass, refactor for maintainability, and run the full suite to verify coverage targets.

What is the best way to structure unit testing and bug fixes to reduce regression risk?

The best way to reduce regression risk during bug fixes is adopting a quality-first approach by writing a failing test that reproduces the bug, implementing the minimal code to pass it, and refactoring safely.

How does the red-green-refactor-verify workflow improve code quality?

The red-green-refactor-verify workflow improves code quality by mandating tests-first design and minimal implementation, ensuring every feature is validated by a failing test before logic is introduced and refactored for maintainability.

Can I integrate structured TDD cycles into existing team review and planning workflows?

Yes, structured TDD cycles integrate directly into development, review, and planning workflows by establishing consistent quality gates that require failing tests and full test suite verification before any feature advances.

What are the limitations of applying minimal implementation rules in test-driven development?

A limitation of minimal implementation in test-driven development is that it requires strict discipline; developers must write only enough code to pass the failing test before refactoring, which can initially slow down feature delivery speed.