nw-tdd-review-enforcement

Enforce TDD design mandates and test budgets during code reviews.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/StudentCristian/nWave-github --skill nw-tdd-review-enforcement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-tdd-review-enforcement
Source: https://github.com/StudentCristian/nWave-github/tree/main/.github/skills/nw-tdd-review-enforcement
Command: npx skills add https://github.com/StudentCristian/nWave-github --skill nw-tdd-review-enforcement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and standardizes TDD reviews by enforcing test design mandates, budget constraints, and external validity checks, reducing human error and review time.

Core Features & Use Cases

  • Enforces observable behavioral outcomes and prevents testing of internal structures.
  • Validates that tests are routed through driving ports (application services, controllers, CLI handlers, event handlers) and discourages domain-layer unit tests.
  • Performs 5-phase TDD validation (PREPARE, RED_ACCEPTANCE, RED_UNIT, GREEN, COMMIT) and checks for external validity across adapters and entry points.
  • Applies a formal test budget model: max_unit_tests = 2 x number_of_distinct_behaviors, guiding test suite scope and preventing budget bloat.

Quick Start

Run the enforcement pass against your project to verify 5 design mandates, test budget, and external validity rules.

Frequently Asked Questions about nw-tdd-review-enforcement

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

FAQPage Schema
How do I enforce TDD design mandates during code reviews?

Validate TDD compliance by running an enforcement pass that checks five phases: PREPARE, RED_ACCEPTANCE, RED_UNIT, GREEN, and COMMIT. This ensures tests target observable behaviors and routing through driving ports is maintained.

What is the test budget model for limiting unit tests in TDD?

The test budget model limits unit tests by setting a maximum threshold where max_unit_tests equals twice the number of distinct behaviors. This prevents test suite bloat and guides the overall scope of your testing efforts.

How do I ensure external validity when testing through driving ports?

Ensure external validity by validating that tests are routed through driving ports like application services, controllers, CLI handlers, and event handlers. This approach discourages domain-layer unit tests and checks validity across adapters and system entry points.

Can I use automated TDD enforcement for QA workflows and adapter validation?

Yes, you can apply automated TDD enforcement to QA workflows and adapter validation. It verifies compliance with design mandates, checks external validity across system entry points, and prevents the testing of internal structures.

When should I discourage domain-layer unit tests in my testing strategy?

Discourage domain-layer unit tests when enforcing driving-port-based testing strategies. Route tests through application services, controllers, or event handlers to ensure external validity and verify observable behavioral outcomes rather than internal structures.