nw-taste-evaluation

Evaluate design options using DVF filtering and four taste criteria.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Taste is tacit and subjective in design decisions; this Skill provides a structured, auditable framework to quantify and compare design options using the DVF filter and explicit taste criteria.

Core Features & Use Cases

  • DVF primary filter to triage options quickly and consistently.
  • Four taste criteria (Subtraction, Concept Count, Progressive Disclosure, Speed-as-Trust) with explicit rubrics.
  • Weighted scoring matrix to produce a defendable ranking of options.
  • Use Case: teams evaluating multiple design options to decide which to advance in a product roadmap.

Quick Start

Enter your design options and let the system score them against the DVF criteria.

Frequently Asked Questions about nw-taste-evaluation

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

FAQPage Schema
How do I quantify taste when evaluating multiple design options for a product roadmap?

The DVF primary filter triages design options quickly and consistently, while four taste criteria (Subtraction, Concept Count, Progressive Disclosure, Speed-as-Trust) apply explicit rubrics. This structured process prevents tacit, subjective preferences from dominating product strategy decisions.

How do I use a weighted decision matrix to rank design options for product management?

To rank design options, input them into the taste evaluation framework. The system applies the DVF filter and T1-T4 taste rubrics, calculating weighted scores that produce a defendable option ranking for product roadmap decisions.

What are the four taste criteria used to score product design decisions?

The four taste criteria used to score product design options are Subtraction, Concept Count, Progressive Disclosure, and Speed-as-Trust. Each criterion applies an explicit T1-T4 rubric to evaluate and quantify design taste consistently.

Can I use this taste evaluation framework for any scale of product management decisions?

This taste evaluation framework is designed for teams evaluating multiple design options to decide which to advance in a product roadmap. It provides an auditable structure for product strategy decisions, regardless of the specific product scale.

Why should I use a DVF filter instead of subjective preferences for design option ranking?

You should use a DVF filter because taste is tacit and subjective in design decisions. The DVF filter provides a structured, auditable framework to triage options quickly and consistently, ensuring your option ranking is defendable rather than arbitrary.