tdd-workflow

Enforce a strict TDD workflow through the RED-GREEN-IMPROVE cycle.

12|4|Updated Mar 14, 2026

Search Tags:#workflow #testing #tdd #quality-assurance #development-process

Ready to run

npx skills add https://github.com/mshadmanrahman/pm-pilot --skill tdd-workflow-mshadmanrahman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/mshadmanrahman/pm-pilot/tree/main/skills/dev/tdd-workflow
Command: npx skills add https://github.com/mshadmanrahman/pm-pilot --skill tdd-workflow-mshadmanrahman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a strict test-driven development workflow by guiding teams through the RED-GREEN-IMPROVE cycle to ensure tests drive implementation.

Core Features & Use Cases

Phased TDD cycle: RED, GREEN, and IMPROVE phases with framework-agnostic commands.
Guardrails & checks: Fail-first testing discipline, minimal implementation, and refactoring discipline with coverage checks.
Use Case: When adding a new feature or fixing a bug, the workflow ensures tests are written before code and kept green through iteration.

Quick Start

Trigger the first RED phase by writing a failing test and executing the appropriate test framework command for your project.

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 workflow for feature development and bug fixes?▼

To enforce a test-driven development workflow, you guide the code changes through the RED-GREEN-IMPROVE cycle. This ensures failing tests precede implementation, driving minimal viable code and quality assurance checks.

What is the RED-GREEN-IMPROVE cycle in test-driven development?▼

The RED-GREEN-IMPROVE cycle in test-driven development is a phased testing workflow. RED requires writing a failing test first, GREEN implements minimal viable code to pass it, and IMPROVE refactors with coverage checks.

How do I start the RED phase for TDD using my existing testing framework?▼

To start the RED phase for TDD, write a failing test for your new feature or bug fix, then execute the appropriate test framework command for your project to verify the test fails before implementation.

Can I use this TDD workflow for refactoring existing code, or is it only for new features?▼

You can use this TDD workflow for refactoring existing code, as well as feature development and bug fixes. The IMPROVE phase specifically applies refactoring discipline while maintaining coverage checks to keep tests green.

Does this test-driven development workflow require a specific testing framework?▼

This test-driven development workflow does not require a specific testing framework. It uses framework-agnostic commands during the RED, GREEN, and IMPROVE phases to ensure tests drive implementation across different environments.

Why does TDD require writing a failing test before writing the implementation code?▼

TDD requires writing a failing test before implementation to enforce fail-first testing discipline. This ensures the code change is necessary and that tests genuinely drive the minimal viable code through the RED-GREEN-IMPROVE cycle.