skills.rest
barbosakjn
barbosakjnCOMMUNITY
Explore all skills by this author →
GitHub

tdd-workflow

Automate the RED-GREEN-REFACTOR cycle for Test-Driven Development workflows.

1|Updated Dec 28, 2025
Search Tags:#testing#tdd#qa#red-green-refactor#best-practices#software-development#engineering-workflow
One-click install
npx skills add https://github.com/barbosakjn/finance-app --skill tdd-workflow-barbosakjn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/barbosakjn/finance-app/tree/main/.agent/workflows/.agent/skills/tdd-workflow
Command: npx skills add https://github.com/barbosakjn/finance-app --skill tdd-workflow-barbosakjn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines and standardizes how teams adopt Test-Driven Development by providing a clear, repeatable workflow that emphasizes writing tests before production code.

Core Features & Use Cases

  • RED-GREEN-REFACTOR cycle: a structured approach for failing tests, minimal production code, and subsequent refactoring.
  • Laws, patterns & best practices: enforces the three TDD laws and the AAA testing pattern to improve test quality and code clarity.
  • Use cases: ideal for new features, bug fixes, and exploratory work where design is driven by tests.

Quick Start

Start with a failing test, implement the minimal production code to pass, then 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?▼

The RED-GREEN-REFACTOR cycle in Test-Driven Development is a structured approach where you write a failing test, implement minimal production code to pass it, and then refactor. This workflow ensures tests drive software design and maintainability.

How do I apply the three laws of TDD to my software development workflow?▼

To apply the three laws of TDD, follow a structured workflow that enforces writing tests before production code and utilizes the AAA testing pattern. This approach guides teams through cycles to improve code clarity and quality.

When should I use Test-Driven Development for bug fixes and exploratory work?▼

Test-Driven Development is ideal for bug fixes and exploratory work where tests drive design. By starting with a failing test that captures the bug, you implement minimal code to pass it and refactor safely.

What's the best way to structure tests using the AAA pattern in TDD?▼

The best way to structure tests using the AAA pattern in TDD is to follow the RED-GREEN-REFACTOR cycle, enforcing the three TDD laws. This ensures Arrange, Act, Assert phases drive quality and maintainable code.

Does Test-Driven Development work for new feature development without existing tests?▼

Yes, Test-Driven Development works perfectly for new feature development. You start by writing a failing test for the desired feature, implement the minimal production code to pass it, and then refactor to improve design.

Why does writing tests before production code improve software engineering workflow?▼

Writing tests before production code improves software engineering workflows by enforcing the three TDD laws and the AAA pattern. This structured approach ensures tests drive quality, clarify design, and maintain code integrity.

Related Skills

Explore More Software Engineering Skills→
AvatarGanymedeAvatarGanymede

e2e

Automate end-to-end web application testing with Playwright.

Community
Advanced
Sheldon-92Sheldon-92
3

Testing

Execute test suites and report failures with coverage metrics.

Community
Intermediate
lastcowlastcow

innozverse-testing-quality

Enforce linting, type checking, formatting, and build checks for the innozverse project.

Community
Intermediate
maystudiosmaystudios
10

tdd

Guide teams through red-green-refactor cycles with atomic commits per phase.

Community
Intermediate