nw-ad-critique-dimensions

Evaluate acceptance tests across nine quality dimensions and generate remediation notes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps teams identify and improve gaps in acceptance test quality across a comprehensive set of dimensions, ensuring tests cover user value and business outcomes.

Core Features & Use Cases

  • Dimension-driven critique: Evaluates each dimension (happy path bias, GWT format, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability, and boundary proof) and provides concrete remediation.
  • Actionable guidance: Reframes skeletons to be user-centric, flags internal-state assertions, and suggests traceability improvements to link tests to stories and environments.
  • Use Case: A product team reviews an existing acceptance test suite and receives a structured report with prioritized issues and concrete rewrites.

Quick Start

Review an existing skill's acceptance tests, run the critique, and publish the recommended changes to the test suite.

Frequently Asked Questions about nw-ad-critique-dimensions

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

FAQPage Schema
How do I identify gaps in acceptance test quality across multiple dimensions?

To identify gaps in acceptance test quality, apply nine evaluation dimensions including happy path bias, GWT format, and traceability coverage to generate actionable remediation notes with prioritized issues and concrete rewrites.

What is the best way to reframe walking skeleton tests to be user-centric?

The best way to reframe walking skeleton tests for user-centricity is to evaluate them against priority validation and boundary proof dimensions, flagging internal-state assertions and suggesting rewrites that emphasize observable user outcomes.

How do I review acceptance tests for Given-When-Then format and business language purity?

Review acceptance tests by checking GWT format and business language purity dimensions, ensuring tests avoid internal state assertions and establish clear traceability to user stories and environments for actionable improvements.

Does this acceptance test critique approach work for existing test suites?

Yes, this acceptance test critique approach works for existing suites by reviewing provided skill content, applying coverage completeness and traceability dimensions, and publishing a structured report with recommended changes.

How do I fix happy path bias and lack of boundary proof in acceptance testing?

Fix happy path bias and boundary proof issues by applying the walking skeleton boundary proof evaluation dimension, which provides concrete remediation notes that prioritize user-centric outcomes over internal state validation.