tdd-workflow

Guide Red-Green-Refactor cycles and enforce 80% test coverage.

20|3|Updated Apr 30, 2026

Search Tags:#testing #tdd #red-green-refactor #code-quality #quality-assurance #software-development

Ready to run

npx skills add https://github.com/DVNghiem/FlowDeck --skill tdd-workflow-dvnghiem

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/DVNghiem/FlowDeck/tree/main/src/skills/tdd-workflow
Command: npx skills add https://github.com/DVNghiem/FlowDeck --skill tdd-workflow-dvnghiem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams adopt Test-Driven Development by guiding Red-Green-Refactor cycles and enforcing a minimum of 80% test coverage.

Core Features & Use Cases

Automated test planning: define tests before code to drive design and reduce regression risk.
Guarded implementation: require passing tests before merging or deploying features, fixes, or refactors.
Quality assurance: maintain 80%+ coverage and track refactor safety with built-in checkpoints.

Quick Start

Activate the TDD workflow when starting a new feature, fixing a bug, or refactoring to guide you through Red-Green-Refactor.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema

How do I enforce Test-Driven Development discipline in my software development workflow?▼

You can enforce Test-Driven Development by guiding Red-Green-Refactor cycles and requiring an 80% test coverage minimum. This workflow applies to feature development, bug fixes, and refactoring, ensuring reliable and maintainable code through automated validation.

What is the Red-Green-Refactor cycle and how does it improve code quality?▼

The Red-Green-Refactor cycle is a Test-Driven Development process where you define failing tests first, create minimal implementations to pass them, and then refactor safely. It improves code quality by driving design through tests and reducing regression risk.

How do I maintain 80% test coverage during refactoring and bug fixes?▼

You maintain 80% test coverage during refactoring and bug fixes by using built-in quality assurance checkpoints. The workflow enforces this coverage minimum and tracks refactor safety through automated validation before merging or deploying.

Can I use this TDD workflow for both new features and bug fixes?▼

Yes, you can use this TDD workflow for both new features and bug fixes. It provides structured workflows and quality gates across the entire codebase, requiring clear test definitions and passing automated validation before any code changes are merged.

Do I need automated validation to apply Test-Driven Development to my codebase?▼

Yes, automated validation is required to apply Test-Driven Development effectively. The workflow relies on automated tests to guard implementation, ensuring that minimal code implementations pass defined tests before merging or deploying features.

What is the best way to start test planning for a new software feature?▼

The best way to start test planning is to define your tests before writing any code. This automated test planning approach drives software design, reduces regression risk, and initiates the Red-Green-Refactor cycle for reliable feature development.