tdd

Implement test-driven development cycles from PLAN-*.md feature plans.

41|15|Updated Mar 1, 2026

Search Tags:#tdd #collaboration #red-green-refactor #test-driven-development #task-spec #auto-mode #feature-plan

Ready to run

npx skills add https://github.com/foyzulkarim/skills --skill tdd-foyzulkarim

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/foyzulkarim/skills/tree/main/dev-pipeline/skills/tdd
Command: npx skills add https://github.com/foyzulkarim/skills --skill tdd-foyzulkarim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps developers anchored in a disciplined RED-GREEN-REFACTOR workflow so that every requirement from a task spec becomes verified, incremental work instead of unstructured coding or unchecked assumptions.

Core Features & Use Cases

Dual operational modes: collaborate by pausing at every red and green checkpoint, or run autonomously with an auto flag while still honoring TDD discipline.
Plan-driven execution: ingests a PLAN-*.md feature plan to understand requirements, test plans, scope boundaries, and expected files before implementing anything.
TDD stewardship: enforces one failing test at a time, careful failure analysis, minimal production code, and targeted refactors before moving on to the next scenario, culminating in a structured summary for review.

Quick Start

Ask the tdd skill to implement task T1 from PLAN-auth-login-flow.md in collaborative mode.

Frequently Asked Questions about tdd

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

FAQPage Schema

How do I implement test-driven development from a feature plan?▼

To implement test-driven development, provide a PLAN-*.md feature plan file and request TDD support for a specific listed task. The system enforces strict RED-GREEN-REFACTOR discipline to transform task specifications into reliable, incremental code.

What is the RED-GREEN-REFACTOR cycle and how does it verify code?▼

The RED-GREEN-REFACTOR cycle enforces writing one failing test at a time, confirming the correct failure, writing minimal production code to pass it, and performing targeted refactors. This ensures every requirement becomes verified work instead of unstructured coding.

Can I run test-driven development autonomously without pausing for confirmation?▼

Yes, you can run test-driven development autonomously by using the auto flag. This mode executes the RED-GREEN-REFACTOR workflow continuously while still honoring TDD discipline and scope boundaries, culminating in a structured summary for review.

Does collaborative TDD mode pause at every test failure and success?▼

Yes, collaborative mode pauses at every red and green checkpoint during the test-driven development cycle. This allows developers to analyze failures and confirm minimal code passes before moving forward to the next scenario.

How do I prevent scope creep when writing tests and production code?▼

To prevent scope creep, the TDD workflow ingests your PLAN-*.md file to understand requirements, test plans, and scope boundaries before implementing anything. It enforces respect for these boundaries by handling one failing test at a time.

What format does the feature plan need to be in for TDD task execution?▼

The feature plan must be a PLAN-*.md file. This plan-driven execution format provides the necessary requirements, test plans, scope boundaries, and expected files needed before implementing any code.