ctdd

Coordinates RED, GREEN, and QA agents for discipline-driven TDD workflows.

65|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/joshft/correctless --skill ctdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ctdd
Source: https://github.com/joshft/correctless/tree/main/correctless/skills/ctdd
Command: npx skills add https://github.com/joshft/correctless --skill ctdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a discipline-driven TDD workflow by coordinating distinct agents for RED, GREEN, and QA phases to ensure tests drive implementation.

Core Features & Use Cases

  • Explicit separation of concerns, with separate agents handling test writing (RED), implementation (GREEN), and validation (QA) to prevent information leakage and improve fault isolation.
  • Intensity configuration, progress visibility, including mandatory QA and checkpointing to resume from the last completed phase.
  • Integration with spec artifacts and architecture documentation to ensure tests align with the project’s constraints and entrypoints.

Quick Start

Start the CTDD workflow by running /cspec to generate a spec-driven test plan and begin the RED phase.

Frequently Asked Questions about ctdd

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

FAQPage Schema
How do I enforce strict test-driven development phases in my software workflow?

Multi-agent orchestration enforces strict test-driven development by coordinating distinct agents for RED, GREEN, and QA phases. This prevents information leakage and improves fault isolation by ensuring tests drive implementation across separate pipeline stages.

What is the best way to automate spec-to-test pipelines for code quality?

Spec-to-test pipelines are automated by integrating spec artifacts and architecture documentation. This ensures tests align with project constraints and entrypoints, mandating phase separation and quality assurance validation across feature development.

How do I separate test writing from implementation to prevent information leakage?

Separate test writing from implementation by assigning distinct agents to RED and GREEN phases. This explicit separation of concerns prevents information leakage and improves fault isolation during the test-driven development workflow.

Can I resume a TDD workflow from the last completed phase if development is interrupted?

Yes, you can resume the TDD workflow from the last completed phase. The orchestration provides checkpointing capabilities and progress visibility, allowing development to restart without losing prior test or implementation state.

Do I need architecture documentation to run a disciplined TDD workflow?

Yes, architecture documentation is required. The workflow requires integration with ARCHITECTURE.md and spec artifacts to ensure generated tests align with project constraints and entrypoints before implementation begins.

How do I configure intensity controls for software testing workflows?

Intensity controls for software testing are configured through .correctless/config/workflow-config.json. This file manages the strictness of the pipeline rules governing test writing, audit, implementation, and quality assurance.