recursive-tdd

Enforce RED-GREEN-REFACTOR TDD cycles with mandatory Phase 3 artifacts.

128|10|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/try-works/recursive-mode --skill recursive-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recursive-tdd
Source: https://github.com/try-works/recursive-mode/tree/main/skills/recursive-tdd
Command: npx skills add https://github.com/try-works/recursive-mode --skill recursive-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a strict RED-GREEN-REFACTOR discipline for Phase 3 implementation work in recursive-mode, ensuring a failing test guides all production changes and providing audit-ready records.

Core Features & Use Cases

  • Red-Green-Refactor discipline: Mandates a failing test first, a minimal green implementation, and a safe refactor, recorded in Phase 3 artifacts.
  • Artifact-driven workflow: Guides evidence logging, traceability, and decision records to support auditable software delivery.
  • Model-guided prompts: Supplies structured prompts and templates to drive Phase 3 work and maintain alignment with recursive-mode tooling.

Quick Start

Begin Phase 3 work by writing a failing test first, then implement minimal code to pass.

Frequently Asked Questions about recursive-tdd

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

FAQPage Schema
How do I enforce strict test-driven development for recursive-mode implementation work?

To enforce strict test-driven development in recursive-mode, you mandate a RED-GREEN-REFACTOR cycle where a failing test is written before any production code changes. This ensures all implementation work is guided by verification.

What is the RED-GREEN-REFACTOR cycle and how does it apply to Phase 3 changes?

The RED-GREEN-REFACTOR cycle is a test-driven development process requiring a failing test first, minimal code to pass it, then safe refactoring. For Phase 3 changes, it enforces strict discipline and artifact recording for audit trails.

How do I create audit-ready records for TDD implementation changes?

You create audit-ready records for TDD changes by using artifact-driven workflows that log evidence, traceability, and decision records. This specifies required artifact structures and evidence locations for compliance.

Does recursive-mode Phase 3 require a failing test before writing production code?

Yes, recursive-mode Phase 3 requires a failing test before any production code is written. This strict TDD discipline ensures that all implementation changes are verified and guided by failing tests.

What templates and prompts are available to drive Phase 3 TDD work?

Model-guided prompts and structured templates are supplied to drive Phase 3 TDD work. These templates specify the required artifact structure and evidence locations to maintain alignment with recursive-mode tooling.

When should I not use strict TDD for recursive-mode changes?

Strict TDD for recursive-mode may not suit exploratory prototyping or throwaway spikes where audit trails and artifact recording are unnecessary overhead. It is designed for Phase 3 implementation work requiring compliance.