skills.rest
6BNBN
6BNBNCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforce the Red-Green-Refactor cycle with failing tests before production code.

134|12|Updated Feb 20, 2026
Search Tags:#code quality#testing#tdd#debugging#software development#agile
One-click install
npx skills add https://github.com/6BNBN/FlowPilot --skill test-driven-development-6bnbn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/6BNBN/FlowPilot/tree/main/%E5%85%BC%E5%AE%B9codex%40cursor%E4%B8%80%E9%94%AE%E5%AE%89%E8%A3%85%E6%8A%80%E8%83%BD/codex%E4%B8%80%E9%94%AE%E5%AE%89%E8%A3%85%E6%8A%80%E8%83%BD/.codex-home-claude-parity/skills/test-driven-development
Command: npx skills add https://github.com/6BNBN/FlowPilot --skill test-driven-development-6bnbn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a rigorous Test-Driven Development (TDD) workflow, ensuring that all new code is written with comprehensive tests that fail before implementation, thereby preventing bugs and improving code reliability.

Core Features & Use Cases

  • Enforces TDD Cycle: Guides users through the Red-Green-Refactor cycle.
  • Prevents Regressions: Ensures that tests are written before any production code.
  • Use Case: When developing a new user authentication feature, this Skill ensures you write tests for login, logout, and password reset scenarios before writing the actual authentication logic, guaranteeing the feature works as intended and preventing future bugs.

Quick Start

Always write a failing test before writing any new implementation code.

Frequently Asked Questions about test-driven-development

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

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

Test-driven development requires writing a failing test before writing any implementation code. You start by defining the expected behavior in a test, running it to confirm it fails, then writing the minimal production code to make it pass.

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

The Red-Green-Refactor cycle is the core mechanism of test-driven development. Red means writing a failing test, Green means writing code to make the test pass, and Refactor means improving the code quality without changing its behavior.

How do I fix bugs using test-driven development?▼

To fix bugs using test-driven development, you write a failing test that reproduces the specific bug first. Once the test reliably fails, you write the production code fix to make the test pass, preventing future regressions.

Why does test-driven development prevent code regressions?▼

Test-driven development prevents code regressions by mandating comprehensive tests before implementation. This ensures all new software features have failing tests that verify the intended behavior, safeguarding future code changes from breaking existing functionality.

When should I not use test-driven development for software development?▼

Test-driven development might be bypassed when exploring throwaway prototypes or spiking unknown technical solutions. However, this Skill addresses common rationalizations for skipping TDD and enforces it for all new features and bug fixes to ensure code quality.

Related Skills

Explore More Software Engineering Skills→
heyallencaoheyallencao
118

test-first

Generate failing tests upfront and iteratively develop code to pass them.

Community
Intermediate
dwalleckdwalleck
1

test-driven-development

Guide developers through the Red-Green-Refactor cycle with test-first principles.

Community
Intermediate
aibangjuxinaibangjuxin
2

sprint-prioritizer

Prioritize product backlogs using RICE and MoSCoW frameworks.

Community
Intermediate
szaherszaher

speckit-specify

Generate feature specifications with user stories and acceptance criteria.

Community
Advanced