skills.rest
jwilger
jwilgerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tdd-constraints

Enforce a strict RED to DOMAIN to GREEN to DOMAIN TDD cycle.

Updated Jul 1, 2026
Search Tags:#tdd#discipline#sdlc#phases#workflows#test-driven-development#domain-modeling
One-click install
npx skills add https://github.com/jwilger/claude-code-plugins --skill tdd-constraints
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-constraints
Source: https://github.com/jwilger/claude-code-plugins/tree/main/sdlc/skills/tdd-constraints
Command: npx skills add https://github.com/jwilger/claude-code-plugins --skill tdd-constraints

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a rigorous framework for implementing Test-Driven Development (TDD) with strict phase boundaries to prevent domain-modeling drift, ensuring tests drive design and domain concepts from the start.

Core Features & Use Cases

  • Enforces a four-phase TD cycle: RED → DOMAIN → GREEN → DOMAIN, with explicit checks and ownership.
  • Promotes domain modeling at each checkpoint to avoid primitive obsession and unclear invariants.
  • Applies to any language or test framework, enabling drill-down testing and disciplined iteration.

Quick Start

Start with a single red test, pause for DOMAIN review, create domain types as stubs, implement the minimal green code, then perform post-green domain review and repeat for next criteria.

Frequently Asked Questions about tdd-constraints

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

FAQPage Schema
How do I enforce strict phase boundaries in test-driven development?▼

You enforce strict TDD phase boundaries by following a RED → DOMAIN → GREEN → DOMAIN cycle with explicit phase ownership, ensuring single well-scoped tests, early domain modeling, and minimal green implementations.

What's the best way to prevent domain-modeling drift during TDD?▼

Preventing domain-modeling drift requires pausing for domain review checkpoints between red and green phases, ensuring tests drive design and domain concepts from the start while avoiding primitive obsession.

Can I apply disciplined TDD workflows with any programming language and test framework?▼

Yes, disciplined TDD workflows apply across any language and test framework, enabling drill-down testing and disciplined iteration without relying on specific framework dependencies.

How do I start a TDD cycle with domain modeling checkpoints?▼

Start with a single red test, pause for domain review, create domain types as stubs, implement the minimal green code, then perform a post-green domain review and repeat for the next criteria.

Why does my test-driven development cycle produce unclear invariants?▼

Unclear invariants often result from skipping domain modeling checkpoints, which is why the TDD cycle requires domain review phases to create domain language and prevent primitive obsession.

Does structured TDD require one-assertion tests and non-overlapping phase boundaries?▼

Yes, structured TDD requires single, well-scoped one-assertion tests and non-overlapping phase boundaries to ensure minimal green implementations and maintain domain language integrity.

Related Skills

Explore More Software Engineering Skills→
Orda-by-MoveOrda-by-Move

lab-init

Generates configuration and baseline tracking files for new webnovel projects.

Official
Advanced
treejhtreejh

tdd

Enforce Red-Green-Refactor cycles with failing tests, minimal code, and coverage checks.

Community
Intermediate
posiposiposiposi

tdd-workflow

Guides teams through Red-Green-Refactor cycles for Test-Driven Development across DDD-aligned architecture layers.

Community
Intermediate
freekmurzefreekmurze
997

fix-github-issue

Automate GitHub issue fixes on feature branches with local tests and PR creation.

Community
Advanced