SweetClaude TDD

Coordinate test-writer and implementer subagents through a structured TDD workflow.

6|3|Updated Apr 12, 2026

Search Tags:#automation #git #testing #tdd #quality-assurance #behavioral-contracts

Ready to run

npx skills add https://github.com/carson-sweet/sweetclaude --skill sweetclaude-tdd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: SweetClaude TDD
Source: https://github.com/carson-sweet/sweetclaude/tree/main/skills/code-tdd
Command: npx skills add https://github.com/carson-sweet/sweetclaude --skill sweetclaude-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent development quality and lack of traceability by enforcing a strict Test-Driven Development (TDD) process that links code implementation directly to behavioral contracts and success criteria.

Core Features & Use Cases

Process Control: Manages development lifecycle through a process-control ledger, ensuring budget and quality standards are met before agent dispatch.
Multi-Level TDD: Supports varying levels of rigor, from simple hotfixes to full Gherkin-based feature development with QA caucus reviews.
Immutable Contracts: Ensures test files remain immutable during implementation, preventing scope creep and ensuring that implementation strictly satisfies defined behavioral requirements.

Quick Start

Invoke the code-tdd skill to initiate a new feature development process following the standard TDD workflow.

Frequently Asked Questions about SweetClaude TDD

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

FAQPage Schema

How do I enforce strict Test-Driven Development workflows with immutable behavioral contracts?▼

Test-Driven Development workflows are enforced by coordinating test-writer and implementer subagents against frozen success criteria, ensuring test files remain immutable during implementation to prevent scope creep and guarantee behavioral contract adherence.

What is the RED-GREEN-REFACTOR cycle and how does it apply to automated testing?▼

The RED-GREEN-REFACTOR cycle is a strict Test-Driven Development process applied to software lifecycles, coordinating subagents to write failing tests first, implement code to pass them, and then refactor while maintaining automated QA verification and traceability.

How do I manage process-control ledgers and git worktree isolation for TDD?▼

Process-control ledgers manage development lifecycles by ensuring budget and quality standards are met before agent dispatch, while git-based worktree isolation provides separate environments for strict Test-Driven Development cycles.

Can I use Gherkin-based feature development with automated QA caucus reviews?▼

Gherkin-based feature development with QA caucus reviews is fully supported, allowing varying levels of Test-Driven Development rigor from simple hotfixes to full behavioral contract validation with high traceability.

Does this TDD approach support preventing scope creep during code implementation?▼

Preventing scope creep during code implementation is achieved by keeping test files immutable, ensuring that the implementation phase strictly satisfies the originally defined behavioral requirements and frozen success criteria without deviation.

When do I need behavioral contracts and traceability in software quality assurance?▼

Behavioral contracts and traceability are needed in software quality assurance when development requires high consistency, linking code implementation directly to success criteria through a structured Test-Driven Development process and automated verification.