tdd-workflow

Guides the RED-GREEN-REFACTOR cycle for test-driven development.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/BoraPerusic/agents --skill tdd-workflow-boraperusic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/BoraPerusic/agents/tree/main/skills/to%20try/tdd-workflow
Command: npx skills add https://github.com/BoraPerusic/agents --skill tdd-workflow-boraperusic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Traditional software development can drift without disciplined testing; this skill provides a structured Test-Driven Development workflow that enforces the RED-GREEN-REFACTOR cycle to guide design and prevent regressions.

Core Features & Use Cases

  • Structured workflow: RED (write a failing test), GREEN (write minimal code to pass), REFACTOR (improve quality) with clear rules.
  • Phase guidance: Explicit rules for RED, GREEN, and REFACTOR to minimize waste and maximize signal.
  • Onboarding and consistency: Useful for teams adopting TDD or onboarding new developers; ensures consistent practice across features and projects.
  • Use Case: A developer adds a new feature by first creating a failing test, implementing just enough code to pass, then refactoring while keeping all tests green.

Quick Start

Follow the RED-GREEN-REFACTOR cycle to drive feature development from a failing test to a passing implementation and subsequent refactor.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
What is the RED-GREEN-REFACTOR cycle in test-driven development?

You can use test-driven development for feature development, bug fixes, and exploratory coding. It applies to scenarios where tests define behavior, ensuring consistent practice across features and preventing regressions in your software projects.

How do I implement test-driven development for a new feature?

Test-driven development is ideally suited for teams onboarding new developers or adopting structured software-testing workflows. It provides explicit phase guidance and consistent practice across projects, ensuring disciplined testing without drifting.

Does test-driven development work for fixing bugs and exploratory coding?

Before adopting test-driven development, you need an environment that supports writing and running tests. The workflow outputs a structured narrative with rules for each phase, ensuring consistent practice and preventing regressions across your software engineering projects.

What is the best way to structure a test-driven development workflow?

Test-driven development minimizes waste and maximizes signal by enforcing clear rules for the RED, GREEN, and REFACTOR phases. This structured workflow guides software design and prevents regressions, making it useful for teams adopting TDD.