nw-por-review-criteria

Apply review dimensions and bug patterns to journey artifact reviews.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a formal rubric to assess journey artifact reviews, ensuring consistency, completeness, and actionable feedback across product artifacts.

Core Features & Use Cases

  • Review Dimensions: Journey Coherence, Emotional Arc, Shared Artifact Tracking, Example Data Quality, and CLI UX Patterns to evaluate artifact quality.
  • Four Bug Patterns: Version Mismatch, Hardcoded URLs, Path Inconsistencies, and Missing Commands, with guidance to trace and fix.
  • Review Output: A structured evaluation schema that captures strengths, issues by dimension, artifact details, and recommended actions.

Quick Start

Provide a structured review by applying the criteria to a given journey artifact to surface gaps and risks.

Frequently Asked Questions about nw-por-review-criteria

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

FAQPage Schema
How do I review journey artifacts to surface data quality and UX risks?▼

Journey artifact reviews apply structured criteria like Journey Coherence, Emotional Arc, and CLI UX Patterns to evaluate product artifacts, surfacing gaps and risks in data quality, tracking, and user experience through a formal rubric.

What bug patterns should I check for during artifact tracking reviews?▼

Artifact tracking reviews target four bug patterns: Version Mismatch, Hardcoded URLs, Path Inconsistencies, and Missing Commands. This structured criteria identifies these issues to trace and fix gaps in journey maps and CLI UX.

How does a structured rubric improve product owner review scenarios?▼

A structured rubric improves product owner reviews by quantifying artifact quality across defined dimensions like Example Data Quality and Shared Artifact Tracking, ensuring consistency, completeness, and actionable feedback for journey maps and CLI UX patterns.

Can I evaluate CLI UX patterns using formal review dimensions?▼

Yes, CLI UX patterns are evaluated as a review dimension within the artifact assessment. The rubric checks command-line interface user experience against defined criteria to surface risks and produce structured review output.

What is the best way to structure output for journey artifact evaluations?▼

Journey artifact evaluations produce a structured review output schema capturing strengths, issues by dimension, artifact details, and recommended actions, ensuring consistency and actionable feedback across product artifacts.

Do I need predefined review dimensions to assess artifact quality?▼

Predefined review dimensions like Journey Coherence, Emotional Arc, Shared Artifact Tracking, Example Data Quality, and CLI UX Patterns are needed to formally assess artifact quality and quantify gaps and risks consistently.