tdd-workflow

Name: tdd-workflow
Availability: InStock
Author: skeletorflet

Automate the RED-GREEN-REFACTOR cycle for test-driven development workflows.

7|1|Updated Mar 28, 2026

Search Tags:#workflow #testing #tdd #refactoring #code-quality #dev-process

Ready to run

npx skills add https://github.com/skeletorflet/opencode-kit --skill tdd-workflow-skeletorflet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/skeletorflet/opencode-kit/tree/main/.opencode/skills/tdd-workflow
Command: npx skills add https://github.com/skeletorflet/opencode-kit --skill tdd-workflow-skeletorflet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD workflow champions a test-first approach to reduce defects, accelerate feedback, and clarify requirements before coding.

Core Features & Use Cases

Enforces the RED-GREEN-REFACTOR cadence to drive reliable, maintainable code.
Guides writing tests first and implementing minimal production code to pass.
Use case: teams adopting TDD during feature development, bug fixes, and refactors to improve confidence and code quality.

Quick Start

Write a failing test first, then implement only enough code to pass, and repeat.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema

What is the test-driven development RED-GREEN-REFACTOR cycle?▼

The RED-GREEN-REFACTOR cycle is the core test-driven development workflow of writing a failing test, implementing minimal code to pass it, and then refactoring. It enforces a test-first approach to clarify requirements and reduce defects.

How do I start writing tests first when developing new features?▼

To start writing tests first during feature development, write a failing test that defines the desired behavior, then implement only enough production code to make it pass, and repeat this cycle to build reliable code.

Can I use this test-first workflow for bug fixes and refactoring?▼

Yes, you can use this test-first workflow for bug fixes and refactoring processes. It guides structured code evolution by enforcing clear phase rules, improving confidence and code quality across your software team.

What's the best way to enforce TDD phase rules across a software team?▼

The best way to enforce TDD phase rules is to automate the RED-GREEN-REFACTOR cadence. This ensures developers write tests first and implement minimal production code, driving disciplined code evolution.

Why does writing minimal production code improve code quality?▼

Writing minimal production code to pass tests improves code quality because it prevents over-engineering and ensures every line of code is backed by a test-first requirement, accelerating feedback and clarifying requirements.

When should I not use a strict test-driven development workflow?▼

A strict test-driven development workflow may not suit exploratory prototyping where requirements are highly volatile. It requires a clear understanding of desired behavior upfront to write effective failing tests before implementation.