tdd

Coordinate TDD workflows across AI subagents with one-test-per-cycle discipline.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/drdanmaggs/rocket-fuel --skill tdd-drdanmaggs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/drdanmaggs/rocket-fuel/tree/main/internal/plugin/skills/tdd
Command: npx skills add https://github.com/drdanmaggs/rocket-fuel --skill tdd-drdanmaggs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Test-driven development with context-isolated RED/GREEN/REFACTOR phases. Use when implementing features, fixing bugs, or adding functionality.

Core Features & Use Cases

  • Orchestrates planning, RED/GREEN/REFACTOR phases, and outer-loop acceptance testing.
  • Enforces the one-test-per-cycle gate with gating checks and stepwise commits.
  • Supports plan generation, plan reviews, and regression analysis to ensure robust test coverage.

Quick Start

Instruct the orchestrator to start a TDD session with auto-generated planning and begin the RED phase.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I automate RED GREEN REFACTOR loops for test-driven development?

You can automate RED GREEN REFACTOR loops by orchestrating AI subagents that enforce a one-test-per-cycle discipline, generating structured phase briefs and stepwise commits throughout the TDD workflow.

What is the one-test-per-cycle discipline in TDD and how does it work?

The one-test-per-cycle discipline in TDD enforces writing and validating exactly one test per development cycle using gating checks, ensuring structured progression through RED, GREEN, and REFACTOR phases before moving forward.

How do I start a TDD session with auto-generated planning for feature development?

To start a TDD session, instruct the orchestrator to generate a plan automatically and begin the RED phase, which initiates the structured workflow for feature development or bug-fix scenarios.

Does AI-powered TDD orchestration support regression analysis and acceptance testing?

AI-powered TDD orchestration supports regression analysis and outer-loop acceptance testing by coordinating plan reviews, validation gates, and structured test coverage checks across session-based cycles.

Can I use TDD subagent orchestration for bug-fix scenarios as well as new features?

TDD subagent orchestration applies to both feature development and bug-fix scenarios, routing plans through session-based cycles that include planning, RED GREEN REFACTOR loops, and final acceptance tests.

What are the limitations of enforcing one-test-per-cycle in AI-driven TDD workflows?

Enforcing one-test-per-cycle in AI-driven TDD workflows requires strict adherence to validation gates and stepwise commits, meaning developers cannot batch multiple tests in a single cycle without breaking the structured phase progression.