tdd-discipline

Enforce a red-green-refactor TDD loop with mandatory verification gates.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/tuanldas/superteam --skill tdd-discipline-tuanldas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-discipline
Source: https://github.com/tuanldas/superteam/tree/main/skills/tdd-discipline
Command: npx skills add https://github.com/tuanldas/superteam --skill tdd-discipline-tuanldas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Implementing features or bug fixes often proceeds without tests, leading to fragile code. TDD Discipline ensures you always write a failing test first and follow a strict Red-Green-Refactor cycle with mandatory verification gates, preventing code-before-test shortcuts and catching testing anti-patterns.

Core Features & Use Cases

  • Enforces the Red-Green-Refactor cycle with mandatory verification gates between steps.
  • Prevents code-before-test shortcuts and discourages anti-patterns.
  • Supports monorepo and project-aware testing by pairing with superteam:project-awareness to detect frameworks and test strategies.

Quick Start

Run the TDD workflow with /st:tdd to start a red-green-refactor cycle.

Frequently Asked Questions about tdd-discipline

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

FAQPage Schema
How do I enforce a strict red-green-refactor cycle when writing tests?

TDD discipline enforces red-green-refactor by applying mandatory verification gates between steps, preventing code-before-test shortcuts and catching testing anti-patterns. It blocks progression if the cycle is violated.

What are common testing anti-patterns and how can I prevent them?

Testing anti-patterns like code-before-test shortcuts are prevented by enforcing mandatory verification gates. TDD discipline blocks progression until each red-green-refactor phase is properly validated.

Can I use TDD discipline for both frontend and backend projects?

Yes, TDD discipline applies to feature work, bug fixes, and any verifiable logic across frontend and backend projects. It pairs with project-awareness tools to detect frameworks and tailor test setup.

How do I start a TDD workflow for a new feature or bug fix?

Start the TDD workflow by running the designated command to initiate a red-green-refactor cycle. The system enforces mandatory gates, requiring a failing test first before any implementation.

Does TDD discipline work with monorepo and project-aware testing setups?

Yes, TDD discipline supports monorepo and project-aware testing by integrating with project-awareness components to detect frameworks and ensure tests drive implementation tailored to each project.