tdd-implement

Automate the RED-GREEN-REFACTOR TDD workflow in spec-kit projects.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/chaimt/GarminShabbatMode --skill tdd-implement-chaimt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-implement
Source: https://github.com/chaimt/GarminShabbatMode/tree/main/.cursor/skills/tdd-implement
Command: npx skills add https://github.com/chaimt/GarminShabbatMode --skill tdd-implement-chaimt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates and enforces a disciplined TDD cycle, guiding teams through RED→GREEN→REFACTOR iterations to improve code quality and reduce waste.

Core Features & Use Cases

  • Enforces a strict vertical-slice TDD workflow: write a failing test, implement minimally, and refactor with confidence.
  • Tracks and manages increment states for multiple test scenarios, ensuring repeatable progress across projects using a spec-kit structure.
  • Promotes public-interface testing and robust error handling, reducing reliance on internal implementation details.

Quick Start

Start the workflow by running the tdd.implement command to process the next pending increment.

Frequently Asked Questions about tdd-implement

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

FAQPage Schema
How do I automate the RED GREEN REFACTOR TDD workflow in a spec-kit project?

You can automate the RED GREEN REFACTOR TDD workflow by running the tdd.implement command, which processes the next pending increment and enforces a strict vertical-slice testing cycle.

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

The RED GREEN REFACTOR cycle is a test-driven development workflow where you write a failing test, implement the minimal code to pass it, and then refactor the codebase with confidence to improve quality and reduce waste.

Do I need a specific directory structure to enforce test-driven development increments?

Yes, you need a compatible .specify/ structure and a defined increment state to drive progress, ensuring repeatable test-driven development cycles across multiple scenarios within your project.

How does test-driven development handle multiple test scenarios and increment tracking?

Test-driven development tracks and manages increment states for multiple test scenarios, ensuring repeatable progress across projects by enforcing disciplined test increments through a defined spec-kit structure.

Why should public-interface testing be used over internal implementation testing?

Public-interface testing reduces reliance on internal implementation details, promoting robust error handling and ensuring your tests validate external behavior rather than brittle internal code structures.