skill-tdd

Enforce a red-green-refactor test-driven workflow with mandatory verification phases.

4.0k|369|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/nyldn/claude-octopus --skill skill-tdd-nyldn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-tdd
Source: https://github.com/nyldn/claude-octopus/tree/main/skills/skill-tdd
Command: npx skills add https://github.com/nyldn/claude-octopus --skill skill-tdd-nyldn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing reliable software quickly is hard without a strict testing discipline. This skill codifies a test-driven development workflow that ensures tests guide feature implementation, reducing wasted work and regression risk.

Core Features & Use Cases

  • Red-Green-Refactor cycle with mandatory verification at each stage to ensure progressive correctness.
  • Phase-based guidance for RED, VERIFY RED, GREEN, VERIFY GREEN, and REFACTOR, promoting safe and incremental delivery.
  • Suitable for new features, bug fixes, or behavior changes across codebases, enabling reproducible, high-quality outcomes.

Quick Start

Begin by writing a failing test for the feature and then run the test suite to observe the failure.

Frequently Asked Questions about skill-tdd

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

FAQPage Schema
How do I enforce a test-driven development workflow for new features?

A test-driven development workflow is enforced by automating phase-based guardrails that require writing failing tests before production code, verifying each red, green, and refactor stage to ensure progressive correctness and reduce regression risk.

What is the red-green-refactor cycle and how does it guide software development?

The red-green-refactor cycle is a test-first development process that guides teams through writing failing tests, writing minimal production code to pass tests, and refactoring, with mandatory verification at each stage for safe incremental delivery.

How do I start test-first development for a bugfix or behavior change?

You start test-first development for a bugfix or behavior change by writing a failing test that defines the desired behavior, then running the test suite to observe the failure before writing any production code.

Can I apply test-driven development to any codebase or is it platform specific?

Test-driven development can be applied across codebases for feature, bugfix, or behavior-change tasks, providing phase-based guidance and structured verifications that are platform agnostic and enable reproducible, high-quality outcomes.

Why should I use minimal production code when doing test-driven development?

Minimal production code is used in test-driven development to satisfy requirements for explicit test definitions and iterative verification, ensuring tests guide feature implementation, reducing wasted work, and preventing regression.

What's the best way to structure a test-driven development workflow for a team?

The best way to structure a test-driven development workflow for a team is to codify the process into explicit phases like RED, VERIFY RED, GREEN, VERIFY GREEN, and REFACTOR, promoting safe and incremental delivery with mandatory verifications.