test-driven-development

Enforce a test-first workflow with explicit red-green-refactor cycles.

Updated Apr 25, 2026

Search Tags:#testing #tdd #red-green-refactor #quality-assurance #software-engineering #dev-process

Ready to run

npx skills add https://github.com/tomasbasso/SistemaStockV2 --skill test-driven-development-tomasbasso

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/tomasbasso/SistemaStockV2/tree/main/.agents/skills/desarrollo-guiado-por-pruebas-tdd
Command: npx skills add https://github.com/tomasbasso/SistemaStockV2 --skill test-driven-development-tomasbasso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Software teams often drift away from test discipline, leading to fragile code and regressions. This Skill enforces a test-first mindset, ensuring a failing test exists before any production code is written. It provides a structured cycle of Red-Green-Refactor to maintain quality throughout development.

Core Features & Use Cases

Red-Green-Refactor discipline that codifies the order of operations.
Guardrails for new features, bug fixes, refactoring, and behavior changes.
Clear guidance and examples to recover from regressions and maintain code health.

Quick Start

Write a failing test first, then implement the minimal production code to pass the test, and repeat the Red-Green-Refactor cycle.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema

How do I enforce a test-first workflow for feature development and bug fixes?▼

The red-green-refactor cycle structures test-driven development by first writing a failing test (red), implementing minimal production code to pass it (green), then systematically refactoring while continuously verifying behavior.

What is the red-green-refactor cycle in test-driven development?▼

The red-green-refactor cycle structures test-driven development by writing a failing test (red), implementing minimal code to pass it (green), then systematically refactoring while continuously verifying behavior.

How do I start applying TDD to refactoring existing code safely?▼

Start refactoring with TDD by creating dedicated tests that capture current behavior, ensuring they fail appropriately, then modifying code systematically while continuously verifying that tests pass throughout the process.

Can I use test-driven development for behavior changes in software projects?▼

Yes, test-driven development applies to behavior changes in software projects by codifying the order of operations and providing guardrails to ensure a failing test exists before modifying production code.

Why does writing tests first improve quality assurance in software engineering?▼

Writing tests first improves quality assurance by maintaining a structured test discipline throughout development, which prevents fragile code and regressions while ensuring implementation remains minimal and verifiable.

What are the limitations of applying a strict test-first discipline to all code changes?▼

Strict test-first discipline requires dedicated test creation for every change, which may slow down initial prototyping but ensures systematic refactoring with continuous verification to maintain code health.