tdd-bdd

Guide TDD and BDD practices for software design and verification.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/hung-phan/system-skills --skill tdd-bdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-bdd
Source: https://github.com/hung-phan/system-skills/tree/main/skills/system-review/references/code-design/tdd-bdd
Command: npx skills add https://github.com/hung-phan/system-skills --skill tdd-bdd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses common challenges in software development, such as unclear requirements, refactoring fears, and regression bugs, by promoting Test-Driven Development (TDD) and Behavior-Driven Development (BDD) as core design and verification tools.

Core Features & Use Cases

  • Design Discipline: Encourages writing tests before code to ensure testable, robust designs.
  • TDD vs BDD: Offers insights into the differences between TDD and BDD approaches, including scenarios where they are most effective.
  • Use Case: Use this Skill when starting a new project to establish a strong foundation for testability and collaboration between developers, product managers, and QA.

Quick Start

Run the 'tdd-bdd' skill to understand the principles of TDD and BDD and how they can be applied to your projects.

Frequently Asked Questions about tdd-bdd

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

FAQPage Schema
What is the difference between TDD and BDD methodologies?

TDD focuses on writing tests before code to drive software design, while BDD emphasizes behavior scenarios to align development with requirements. This Skill explains both approaches and their distinct verification roles.

How do I use the red-green-refactor cycle to improve software design?

The red-green-refactor cycle involves writing a failing test, making it pass with minimal code, then refactoring. This Skill provides comprehensive guidance on applying this cycle to ensure testable and robust software designs.

When should I choose classicist vs mockist approaches in Test-Driven Development?

Classicist and mockist approaches differ in how they handle test dependencies and state verification. This Skill covers both methodologies, helping you select the right approach for your specific testing context.

How do I write effective BDD scenarios for unclear product requirements?

BDD scenarios clarify requirements by defining expected behaviors collaboratively. This Skill guides engineers and product managers in creating scenarios that establish strong testability and reduce ambiguity.

What are common pitfalls when applying Test-Driven Development practices?

Common pitfalls in Test-Driven Development include poor test coverage and fragile designs. This Skill outlines these challenges and offers practices to avoid regression bugs and refactoring fears.