nw-test-design-mandates

Enforce four acceptance-test mandates during peer design reviews.

Updated Apr 15, 2026

Search Tags:#test-design #walking-skeleton #pure-functions #acceptance-testing #business-language #driving-port

Ready to run

npx skills add https://github.com/StudentCristian/nWave-github --skill nw-test-design-mandates

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nw-test-design-mandates
Source: https://github.com/StudentCristian/nWave-github/tree/main/.github/skills/nw-test-design-mandates
Command: npx skills add https://github.com/StudentCristian/nWave-github --skill nw-test-design-mandates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Four mandates enforced during peer review to ensure driving-port testing boundaries, business-language abstraction, complete user journeys, walking skeleton strategies, and pure function extraction.

Core Features & Use Cases

Enforce boundary-driven testing through driving ports
Abstract technical details into business language steps
Validate complete user journeys with observable business value
Promote walking skeletons and pure-function extraction

Quick Start

Review your project against the four mandates and implement at least two walking skeletons that drive through entry points.

Frequently Asked Questions about nw-test-design-mandates

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

FAQPage Schema

How do I enforce driving port boundaries in acceptance testing?▼

Driving port boundaries in acceptance testing are enforced by defining compliance criteria that require tests to drive exclusively through entry points. This ensures boundary-driven testing by validating that user journeys interact with driving ports rather than internal implementation details.

What is a walking skeleton strategy for test design?▼

A walking skeleton strategy validates complete user journeys end-to-end by implementing thin slices of functionality that drive through entry points. It guarantees observable business value is validated early by forcing pure-function extraction and driving-port testing across the architecture.

How do I abstract technical test details into business language steps?▼

Abstract technical test details into business language steps by delegating execution through driving ports and enforcing acceptance-test mandates. This shifts test step definitions from implementation-specific calls to observable business-value phrases during peer design reviews.

When do I need to extract pure functions during test design?▼

Extract pure functions during test design when isolating business logic from driving ports and external dependencies. This is needed to enforce compliance criteria for pure-function isolation, ensuring complete user journeys remain testable without side effects during test execution.

Can I use these test design mandates for peer design reviews?▼

Yes, these four acceptance-test mandates are explicitly designed for application during peer design reviews. They enforce boundary-driven testing, business-language abstraction, complete user journeys, walking skeletons, and pure-function extraction by defining strict compliance criteria.

What is the best way to validate complete user journeys with observable business value?▼

The best way to validate complete user journeys with observable business value is implementing walking skeletons that drive through entry points. This approach enforces driving-port testing boundaries and pure-function isolation to guarantee end-to-end value validation.