tdd-interactive

Enforce a five-phase TDD cycle with reviewer-approved verification gates.

Updated Oct 19, 2025
One-click install
npx skills add https://github.com/igor1309/skills --skill tdd-interactive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-interactive
Source: https://github.com/igor1309/skills/tree/main/tdd-interactive
Command: npx skills add https://github.com/igor1309/skills --skill tdd-interactive

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Interactive TDD workflow with reviewer-in-the-loop ensures quality and deliberate progression by requiring explicit human or AI verification at defined gates.

Core Features & Use Cases

  • Two mandatory verification gates (STOP #1 at RED and STOP #2 after REFACTOR) with a reviewer (human or AI) validating work before progression.
  • Five-phase cycle: RED → GREEN → COMMIT → REFACTOR → REFACTOR_COMMIT, with automated transitions and self-review steps.
  • Clear roles and guidance: Executing agent, Reviewer, and escalation protocol for guidance when needed.
  • Encourages alignment with quality standards and executable specifications described in related references.

Quick Start

Begin by writing a failing test and request reviewer approval at STOP #1 before implementing minimal green code.

Frequently Asked Questions about tdd-interactive

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

FAQPage Schema
How do I enforce a structured TDD workflow with reviewer gates?

To enforce a structured TDD workflow with reviewer gates, this Skill implements a five-phase RED → GREEN → COMMIT → REFACTOR → REFACTOR_COMMIT cycle. It requires a living executable specification and mandates explicit verification stops at RED and after REFACTOR.

What is gated development in test-driven development?

Gated development in test-driven development is a process requiring explicit reviewer approval before progressing through phases. This Skill enforces two mandatory verification stops, preventing premature progress during feature development, bug fixes, or refactoring.

How do I start an interactive TDD cycle for a new feature?

To start an interactive TDD cycle, begin by writing a failing test and request reviewer approval at STOP #1. Once approved, implement minimal code to pass the test, commit, refactor, and request approval at STOP #2.

Can I use this interactive TDD workflow for refactoring existing code?

Yes, you can use this interactive TDD workflow for refactoring existing code. It applies to feature development, bug fixes, refactoring, or enhancements across codebases, requiring structured feedback and strict git-history discipline throughout.

What roles are defined in this interactive TDD process?

The interactive TDD process defines clear roles including an Executing agent and a Reviewer. The Reviewer can be human or AI, validating work at defined gates, with an escalation protocol available for guidance when needed.

When should I not use a gated interactive TDD workflow?

You should not use a gated interactive TDD workflow if you lack a living executable specification or cannot accommodate structured feedback stops. The process strictly requires reviewer validation at two phases to maintain quality assurance and deliberate progression.