tdd-workflow

Guide teams through the RED-GREEN-REFACTOR Test-Driven Development cycle.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/gelsonsimoes/wms-verticalparts --skill tdd-workflow-gelsonsimoes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/gelsonsimoes/wms-verticalparts/tree/main/.agent/skills/tdd-workflow
Command: npx skills add https://github.com/gelsonsimoes/wms-verticalparts --skill tdd-workflow-gelsonsimoes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to implementing Test-Driven Development, helping teams prevent over-engineering and reduce debugging time by enforcing a test-first mindset.

Core Features & Use Cases

  • TDD Cycle: Enforces RED-GREEN-REFACTOR workflow for new features.
  • Guidance & Best Practices: Detailed rules like AAA pattern, test naming, and incremental development.
  • Use Case: Adopt TDD in feature development, bug fixes, and refactoring to improve code quality and maintainability.

Quick Start

Walk through a complete TDD cycle for a small feature, applying RED, GREEN, and REFACTOR steps.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How does the test-driven development cycle work for new software features?▼

The test-driven development cycle enforces a RED-GREEN-REFACTOR workflow: write a failing test first, implement the minimum production code to pass it, then refactor while maintaining test coverage.

What is the best way to structure software tests using the AAA pattern?▼

Structure software tests using the AAA pattern by organizing code into Arrange, Act, and Assert segments, ensuring clear test naming conventions and incremental implementation for maintainable test suites.

Can I apply TDD workflows to bug fixes and refactoring existing code?▼

Yes, the TDD workflow applies to bug fixes and refactoring by first writing a test that reproduces the bug or verifies existing behavior, then modifying production code incrementally to pass the updated tests.

Do I need to follow test-first rules to prevent over-engineering in software development?▼

Yes, following test-first rules prevents over-engineering by forcing you to write only the production code necessary to satisfy the specific failing test, reducing unnecessary complexity and debugging time.

How do I prioritize software tests when adopting a TDD workflow?▼

Prioritize software tests using risk-based test prioritization within your TDD workflow, focusing on critical feature paths first to guide incremental development and improve overall code quality.

Why should development teams enforce a structured test-driven development process?▼

Teams should enforce a structured test-driven development process to establish a repeatable TDD cycle, reduce debugging time, and maintain disciplined code quality across feature development and refactoring tasks.