tdd-workflow

Guide developers through the RED-GREEN-REFACTOR cycle for test-first coding.

Updated Sep 2, 2025
One-click install
npx skills add https://github.com/rafaelminatto1/fisioflow-51658291 --skill tdd-workflow-rafaelminatto1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/rafaelminatto1/fisioflow-51658291/tree/main/.agent/skills/tdd-workflow
Command: npx skills add https://github.com/rafaelminatto1/fisioflow-51658291 --skill tdd-workflow-rafaelminatto1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides structured guidance for teams to implement Test-Driven Development by outlining the RED-GREEN-REFACTOR cycle, test naming conventions, and phase discipline to improve code quality and feedback loops.

Core Features & Use Cases

  • Defines the standard TDD cycle (RED, GREEN, REFACTOR) and associated rules.
  • Details how to write tests, how to iterate between phases, and how to maintain test quality.
  • Suitable for any codebase seeking disciplined test-first development and measurable progress.

Quick Start

Follow the RED-GREEN-REFACTOR cycle to write failing tests first, then implement code to pass them.

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?

Test-driven development improves code quality and feedback loops by enforcing a structured test-first approach, requiring you to write failing tests before implementation and applying disciplined test naming conventions.

How do I implement a test-first workflow for my software project?

To implement a test-first workflow, follow the RED-GREEN-REFACTOR cycle: write failing tests first, implement the minimum code to pass them, and then refactor while maintaining disciplined test naming conventions.

Can I apply this test-driven development workflow to any programming language?

Yes, this test-driven development workflow applies to coding tasks across languages and projects, providing structured guidance for any codebase seeking disciplined test-first development and measurable progress.

What are the best practices for test naming in TDD?

Best practices for test naming in TDD involve maintaining disciplined test naming conventions throughout the RED-GREEN-REFACTOR cycle to ensure code quality and clear feedback loops.

When should I not use a strict test-driven development approach?

You should reconsider a strict test-driven development approach if your coding tasks lack measurable progress requirements, as it enforces rigid phase discipline and continuous test quality maintenance.