tdd-workflow

Guide teams through the Red-Green-Refactor cycle with failing tests first.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/aimskr/aims-claude-toolkit --skill tdd-workflow-aimskr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/aimskr/aims-claude-toolkit/tree/main/skills/tdd-workflow
Command: npx skills add https://github.com/aimskr/aims-claude-toolkit --skill tdd-workflow-aimskr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Traditional development can drift without a disciplined testing approach, leading to brittle code and unclear requirements.

Core Features & Use Cases

  • Red-Green-Refactor cycle: Write failing tests first, then implement minimal code to satisfy them.
  • Phase alignment: Define requirements, interfaces, and tests before coding.
  • Quality guardrails: Enforce test coverage and refactoring discipline across features.

Quick Start

Write a failing test for the new feature, then implement only the minimal code required to pass.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I start test-driven development for a new feature?

To start test-driven development, write a failing unit test for the new feature first, then implement only the minimal code required to pass. This enforces the Red-Green-Refactor cycle and ensures requirements are defined before coding.

What is the Red-Green-Refactor cycle in TDD?

The Red-Green-Refactor cycle is a test-driven development workflow where you write a failing test, implement minimal code to satisfy it, and then clean up the design. This cycle maintains measurable test coverage and refactoring discipline.

Can I use TDD workflows during refactoring existing code?

Yes, you can use this test-driven development workflow during refactoring. It enforces quality guardrails by ensuring existing tests pass before and after code changes, supporting clean refactorability and incremental delivery.

Why should I write unit tests before production code?

Writing unit tests before production code prevents traditional development drift by clarifying requirements upfront. This approach enforces test coverage and design quality, resulting in less brittle code and clearer interfaces.

What is the best way to enforce test coverage and quality during feature development?

The best way to enforce test coverage is by adopting a disciplined test-driven development workflow. It aligns phases to define interfaces and tests before coding, establishing quality guardrails across all delivered features.