skill-tdd

Enforce test-first development with failing tests before production code.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/burgebj/claudeoctopus --skill skill-tdd-burgebj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-tdd
Source: https://github.com/burgebj/claudeoctopus/tree/main/.claude/skills/skill-tdd
Command: npx skills add https://github.com/burgebj/claudeoctopus --skill skill-tdd-burgebj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents untested production changes by enforcing a strict test-driven development workflow where failing tests are created before implementation.

Core Features & Use Cases

  • Red-Green-Refactor Enforcement: Guides feature development through failing tests, minimal implementations, verification, and cleanup cycles.
  • Adversarial Test Review: Encourages additional review of test specifications to uncover missing scenarios, edge cases, and weak assertions.
  • Use Case: Use this Skill when adding features, fixing bugs, or changing behavior in software projects that require reliable test coverage and disciplined implementation practices.

Quick Start

Use the skill-tdd skill to implement a new feature while following the complete test-first development workflow.

Frequently Asked Questions about skill-tdd

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

FAQPage Schema
How do I enforce test-driven development when adding new features?

You can enforce test-driven development by applying a strict red-green-refactor cycle that requires creating failing tests before writing any production code. This workflow prevents untested changes by mandating test validation steps prior to implementation.

What is the red-green-refactor cycle in test-first development?

The red-green-refactor cycle is a test-first development process where you write a failing test, implement the minimal code to pass it, and then clean up the implementation. It enforces disciplined software engineering by validating behavior at each step.

Can I use this test-first workflow for bug fixes and behavior changes?

Yes, this test-first workflow applies to bug fixes and behavior changes, not just new features. It requires automated test coverage and verification for any production code modification, ensuring reliable implementation practices across all software changes.

How do I find missing edge cases when writing test specifications?

You can find missing edge cases and weak assertions through an adversarial test review workflow. This process encourages additional review of your test specifications to uncover missing scenarios before production code implementation begins.

Do I need existing automated test coverage to start test-driven development?

No, you do not need existing automated test coverage to start. The test-driven development workflow requires creating new failing tests first, which then establishes the automated test coverage and verification needed before implementing the production code.

Why does test-driven development require failing tests before implementation?

Test-driven development requires failing tests before implementation to prevent untested production changes. This strict discipline ensures that all feature development and behavior changes are verified by automated tests, improving overall code quality.