skills.rest
iadr-dev
iadr-devCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforce a RED-GREEN-REFACTOR loop with failing tests before implementation.

2|Updated Apr 26, 2026
Search Tags:#testing#tdd#red-green-refactor#lint#verifier#behavior-first
One-click install
npx skills add https://github.com/iadr-dev/colab --skill test-driven-development-iadr-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/iadr-dev/colab/tree/main/skills/test-driven-development
Command: npx skills add https://github.com/iadr-dev/colab --skill test-driven-development-iadr-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It prevents “done” work that hasn’t actually been verified by tests, by enforcing a strict RED → GREEN → REFACTOR loop with a verifier gate.

Core Features & Use Cases

  • RED → GREEN → REFACTOR loop: Write a failing test first, make the smallest change to pass, then refactor while staying green.
  • Vertical slicing by behavior: Build one behavior at a time to avoid brittle imagined interfaces.
  • Verifier handoff with concrete checks: Run the exact test command plus static quality checks and block completion on failures or skips.
  • Where it triggers: Activates on keyword “tdd” or when the BUILD workflow is active.

Quick Start

Tell your agent: “Use test-driven-development—write a failing test first, then implement the minimum code to pass, refactor safely, and verify with the provided test and code-quality scripts.”

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How do I enforce a failing test before implementation in my workflow?▼

Test-driven development enforces a strict RED→GREEN→REFACTOR loop, requiring a failing test before implementation and a minimum passing implementation before refactoring to prevent unverified work.

What is the best way to verify code quality and block completion on skipped tests?▼

Code quality verification requires a verifier handoff that runs the exact test command alongside static quality checks, blocking completion if any quality checks fail or tests are skipped.

How does vertical behavior slicing help avoid brittle interfaces during feature implementation?▼

Vertical behavior slicing builds one behavior at a time instead of imagining entire interfaces upfront, ensuring deterministic test-and-quality verification gates validate each specific behavior incrementally.

Can I use test-driven development for BUILD workflow execution tasks?▼

Yes, test-driven development applies to BUILD workflow execution, activating on the keyword “tdd” or when the workflow is active to prove correctness through deterministic test-and-quality verification gates.

When should I not use a RED→GREEN→REFACTOR loop for software changes?▼

You should avoid the RED→GREEN→REFACTOR loop for software changes where correctness cannot be proven through deterministic tests, as the verifier gate strictly blocks completion on failing or skipped tests.

Related Skills

Explore More Software Engineering Skills→
leocostaleocosta
4

test-tdd

Automate an isolated red-green-refactor TDD loop with four phases.

Community
Intermediate
ymkzymkz

inspection-protocol

Enforce post-change verification commands for Gradle and pnpm projects.

Community
Intermediate
riftzen-bitriftzen-bit

verification-loop

Run build, type, lint, test, security, and diff validations with a structured report.

Community
Intermediate
mwaymway
4

tdd-enforce

Enforces test-first discipline for production code changes.

Community
Advanced