skills.rest
Threat-Vector-Security
Threat-Vector-SecurityOFFICIAL
Explore all skills by this author →
WebsiteGitHub

test-driven-development

Guide coding tasks through the Red-Green-Refactor cycle with tests defined before implementation.

11|3|Updated Feb 24, 2026
Search Tags:#testing#refactoring#qa#red-green-refactor#code-quality#unit-tests#test-driven-development
One-click install
npx skills add https://github.com/Threat-Vector-Security/guardian-agent --skill test-driven-development-threat-vector-security
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/Threat-Vector-Security/guardian-agent/tree/main/skills/test-driven-development
Command: npx skills add https://github.com/Threat-Vector-Security/guardian-agent --skill test-driven-development-threat-vector-security

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Test-Driven Development helps teams ensure software behavior is correct by defining tests before implementation, preventing regression and guiding design.

Core Features & Use Cases

  • Red: write a small failing test for a single behavior.
  • Green: implement the minimal production code to pass the test.
  • Refactor: improve design while keeping tests green.
  • Verification: validate that new behavior is covered by tests and that existing tests still pass.

Quick Start

Write a failing test first for the behavior you want to change, then implement the smallest production change to make the test pass.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
What is the test-driven development cycle for writing unit tests?▼

The test-driven development cycle is Red-Green-Refactor: write a failing unit test for a single behavior, implement the minimal production code to pass it, then improve the design while keeping tests green.

How do I practice test-driven development when refactoring legacy code?▼

To practice test-driven development during refactoring, write failing tests that define the expected behavior before changing production code, ensuring correctness and preventing regression while improving maintainability.

When should I use test-driven development for bug fixes?▼

Use test-driven development for bug fixes by first writing a failing unit test that reproduces the specific bug, then applying minimal production changes to make the test pass, verifying the fix without regression.

Can I use test-driven development for writing new software features?▼

Yes, test-driven development applies to coding tasks across projects for new features by defining clear unit tests for desired behaviors before implementation, ensuring code quality and correctness from the start.

Does test-driven development require writing tests before any implementation?▼

Yes, test-driven development enforces writing tests first by requiring clear test definitions before making minimal production changes, guiding software design and ensuring behavior is correct by preventing regression.

What are the limitations of the Red-Green-Refactor approach?▼

The Red-Green-Refactor approach limits rapid prototyping by enforcing small, incremental behavior changes and minimal production code, requiring strict test coverage verification before design improvements can be applied.

Related Skills

Explore More Software Engineering Skills→
caobingshengcaobingsheng
1

tdd-workflows-tdd-red

Generate failing tests to define expected behavior in the TDD red phase.

Community
Advanced
Sheldon-92Sheldon-92
3

Testing

Execute test suites and report failures with coverage metrics.

Community
Intermediate
TeiNamTeiNam
12

laravel-verification

Automate Laravel project verification for CI/CD pipelines.

Community
Advanced
VrooliVrooli
54

Refactor

Refactors complex codebases while preserving behavior and guided by tests, PRD, and documentation.

Official
Advanced