tdd-implementing

Enforce red-green-refactor TDD cycles for feature implementation.

23|2|Updated Jun 9, 2025
One-click install
npx skills add https://github.com/kaptinlin/gozod --skill tdd-implementing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-implementing
Source: https://github.com/kaptinlin/gozod/tree/main/.agents/skills/tdd-implementing
Command: npx skills add https://github.com/kaptinlin/gozod --skill tdd-implementing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill formalizes strict TDD discipline for feature development, ensuring tests drive production code from red to green and refactor.

Core Features & Use Cases

  • Enforced TDD cycle: Ensure RED-GREEN-REFACTOR cycle is followed for each feature.
  • Test-first philosophy: Requires writing failing tests before production code.
  • Workflow integration: Aligns with Code phase tasks, tdd-tasking planning, and planning outputs; guides from planning to checkpoint.
  • Public-interface-focused: Validates behavior through public APIs rather than implementation details.

Quick Start

Announce the skill and begin the red-green-refactor cycle for the current feature.

Frequently Asked Questions about tdd-implementing

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

FAQPage Schema
How do I enforce strict TDD red-green-refactor cycles during feature implementation?

This Skill formalizes strict TDD discipline by enforcing iterative red-green-refactor cycles, requiring failing tests to be written before production code, and guiding feature implementation through public API validation.

What is the best way to drive feature development with test-first workflows?

The best way to drive test-first feature development is to validate behavior through public APIs rather than implementation details, ensuring tests dictate the production code structure throughout the red-green-refactor cycle.

How do I integrate TDD planning outputs into the code phase workflow?

You integrate TDD planning outputs by aligning tdd-tasking planning with code phase tasks, documenting the planning results, and using them to guide strict test-first development from planning to checkpoint.

Do I need a test-first approach to validate behavior through public APIs?

Yes, a test-first approach is required to validate behavior through public APIs. This Skill ensures tests target the public interface rather than internal implementation details during the red-green-refactor cycle.

When should I not use strict TDD cycles for feature implementation?

Strict TDD cycles may not suit exploratory spike work or phases where planning outputs are undefined. The Skill requires a defined public API and documented planning outputs to guide the red-green-refactor loops effectively.