tdd-standard-practice

Standardize a Test-Driven Development workflow using test lists and the Red-Green-Refactor cycle.

2|Updated Feb 12, 2026

Search Tags:#workflow #testing #tdd #refactoring #quality #ci

Ready to run

npx skills add https://github.com/RyoMurakami1983/skills_repository --skill tdd-standard-practice

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-standard-practice
Source: https://github.com/RyoMurakami1983/skills_repository/tree/main/production/tdd-standard-practice
Command: npx skills add https://github.com/RyoMurakami1983/skills_repository --skill tdd-standard-practice

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill standardizes a Test-Driven Development (TDD) workflow to ensure code quality and stability in production environments, balancing speed with safety.

Core Features & Use Cases

Test List Management: Prioritize and select individual behaviors to implement.
Red-Green-Refactor Cycle: Follow the disciplined pattern of writing a failing test, making it pass with minimal code, and then cleaning up.
Use Case: When developing a new feature for a critical system, use this Skill to guide the process, ensuring each behavior is tested before implementation and that the code is clean and maintainable, ultimately reducing bugs and increasing confidence in releases.

Quick Start

Follow the TDD standard practice by writing a test list and then implementing one behavior at a time using the Red-Green-Refactor cycle.

Frequently Asked Questions about tdd-standard-practice

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

FAQPage Schema

What is the standard Test-Driven Development workflow for building production-ready features?▼

Standard Test-Driven Development (TDD) relies on the Red-Green-Refactor cycle and test list management to implement behaviors one by one. This disciplined pattern ensures code quality, reduces bugs, and balances speed with safety in production systems.

How do I implement the Red-Green-Refactor cycle when developing a new feature?▼

To implement the Red-Green-Refactor cycle, start by writing a failing test for a specific behavior from your test list. Next, write the minimal code required to make the test pass, and finally clean up the implementation through refactoring without changing the behavior.

Do I need a local test runner to practice TDD effectively?▼

Yes, a local test runner and a unit test framework are required for Test-Driven Development. A local test runner provides the fast feedback loops necessary to rapidly validate behaviors during the Red-Green-Refactor cycle before integrating changes into CI.

How does TDD improve code quality and stability in critical MVP systems?▼

Test-Driven Development improves stability in MVP systems by enforcing behavior-focused testing before implementation. By managing a test list and validating each specific behavior, developers reduce bugs, maintain clean code, and increase release confidence.

Can I integrate TDD workflows with my existing CI pipeline?▼

Yes, Test-Driven Development workflows emphasize CI integration to ensure reliable code in production environments. By running your behavior-focused unit tests through your CI pipeline, you maintain continuous quality checks alongside rapid local feedback loops.

When should I use a test list during TDD, and what are its limitations?▼

Use a test list during Test-Driven Development to prioritize and select individual behaviors for implementation. A limitation is that it requires a unit test framework; without fast local feedback from a test runner, managing the list becomes a bottleneck rather than an accelerator.