tdd-workflow

sickn33/antigravity-awesome-skills · updated Apr 8, 2026

$npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill tdd-workflow
0 commentsdiscussion
summary

Test-Driven Development workflow guiding the RED-GREEN-REFACTOR cycle.

  • Structured three-phase cycle: write failing tests (RED), implement minimal code to pass (GREEN), then improve code quality (REFACTOR)
  • Emphasizes behavior-driven test design using the AAA pattern (Arrange, Act, Assert) with one assertion per test
  • Provides test prioritization guidance (happy path, error cases, edge cases, performance) and identifies anti-patterns to avoid
  • Supports multi-agent workflows where diff
skill.md

TDD Workflow

Write tests first, code second.


1. The TDD Cycle

🔴 RED → Write failing test
🟢 GREEN → Write minimal code to pass
🔵 REFACTOR → Improve code quality
   Repeat...

2. The Three Laws of TDD

  1. Write production code only to make a failing test pass
  2. Write only enough test to demonstrate failure
  3. Write only enough code to make the test pass

3. RED Phase Principles

What to Write

Focus Example
Behavior "should add two numbers"
Edge cases "should handle empty input"
Error states "should throw for invalid data"

RED Phase Rules

  • Test must fail first
  • Test name describes expected behavior
  • One assertion per test (ideally)

4. GREEN Phase Principles

Minimum Code

Principle Meaning
YAGNI You Aren't Gonna Need It
Simplest thing Write the minimum to pass
No optimization Just make it work

GREEN Phase Rules

  • Don't write unneeded code
  • Don't optimize yet
  • Pass the test, nothing more

5. REFACTOR Phase Principles

What to Improve

Area Action
Duplication Extract common code
Naming Make intent clear
Structure Improve organization
Complexity Simplify logic

REFACTOR Rules

  • All tests must stay green
  • Small incremental changes
  • Commit after each refactor

6. AAA Pattern

Every test follows:

Step Purpose
Arrange Set up test data
Act Execute code under test
Assert Verify expected outcome

7. When to Use TDD

Scenario TDD Value
New feature High
Bug fix High (write test first)
Complex logic High
Exploratory Low (spike, then TDD)
UI layout Low

8. Test Prioritization

Priority Test Type
1 Happy path
2 Error cases
3 Edge cases
4 Performance

9. Anti-Patterns

❌ Don't ✅ Do
Skip the RED phase Watch test fail first
Write tests after Write tests before
Over-engineer initial Keep it simple
Multiple asserts One behavior per test
Test implementation Test behavior

10. AI-Augmented TDD

Multi-Agent Pattern

Agent Role
Agent A Write failing tests (RED)
Agent B Implement to pass (GREEN)
Agent C Optimize (REFACTOR)

Remember: The test is the specification. If you can't write a test, you don't understand the requirement.

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.664 reviews
  • Alexander Kim· Dec 28, 2024

    tdd-workflow reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Maya Wang· Dec 28, 2024

    tdd-workflow fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Ganesh Mohane· Dec 20, 2024

    Registry listing for tdd-workflow matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Hana Smith· Dec 12, 2024

    I recommend tdd-workflow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Advait Sanchez· Dec 4, 2024

    tdd-workflow reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Charlotte Patel· Nov 23, 2024

    Registry listing for tdd-workflow matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Diego Jackson· Nov 19, 2024

    Registry listing for tdd-workflow matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Min Robinson· Nov 19, 2024

    I recommend tdd-workflow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Sakshi Patil· Nov 11, 2024

    tdd-workflow reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Xiao Singh· Nov 11, 2024

    tdd-workflow is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 64

1 / 7