skills.rest
StudentCristian
StudentCristianCOMMUNITY
Explore all skills by this author →
GitHub

nw-po-review-dimensions

Critique requirements documents across five quality dimensions and emit YAML feedback.

Updated Apr 15, 2026
Search Tags:#requirements#testability#clarity#prioritization#completeness#peer-review#bias-detection
One-click install
npx skills add https://github.com/StudentCristian/nWave-github --skill nw-po-review-dimensions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nw-po-review-dimensions
Source: https://github.com/StudentCristian/nWave-github/tree/main/.github/skills/nw-po-review-dimensions
Command: npx skills add https://github.com/StudentCristian/nWave-github --skill nw-po-review-dimensions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Applies structured critique during requirements peer review to surface biases, confirm completeness, ensure clarity, and validate testability and prioritization.

Core Features & Use Cases

  • Provides a multi-dimension checklist (confirmation bias, completeness, clarity, testability, priority) to assess requirements documents.
  • Generates a YAML-style feedback payload that documents issues, severity, and recommendations for editors and stakeholders.
  • Supports review workflows by enforcing non-invocable guidance and blocking issues until addressed.

Quick Start

Activate in review mode to produce a complete YAML feedback payload for the calling agent.

Frequently Asked Questions about nw-po-review-dimensions

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

FAQPage Schema
How do I check requirements for testability and completeness during a peer review?▼

To check requirements during a peer review, apply a multi-dimension checklist assessing confirmation bias, completeness, clarity, testability, and priority validation to surface quality issues systematically.

What is the best way to detect confirmation bias in requirements documents?▼

Detecting confirmation bias in requirements documents involves structured critique during peer review, using targeted dimensions to identify and surface biased assumptions and incomplete prioritization.

How do I generate structured feedback for requirements peer review?▼

Generate structured feedback by activating review mode to produce a YAML-style payload that documents observed issues, severity levels, and actionable recommendations for stakeholders.

Can I enforce blocking issues until requirements are addressed in a review workflow?▼

Yes, you can enforce blocking issues in a review workflow by applying non-invocable guidance that blocks requirements documents from advancing until identified quality issues are fully addressed.

Does peer review work for validating priority and clarity across formal teams?▼

Peer review works for formal requirements reviews across teams by systematically validating priority, ensuring clarity, and applying structured critique to maintain document quality standards.

Related Skills

Explore More Product & Management Skills→
v1bh0rv1bh0r

nw-po-review-dimensions

Evaluate requirements documents against five quality dimensions and produce YAML feedback.

Community
Advanced
ShadylukinShadylukin
74

neumann-troubleshoot

Diagnose Neumann errors, performance problems, and cluster faults.

Community
Advanced
troykellytroykelly
10

comprehensive-review

Review code against seven criteria and post findings to GitHub issues.

Community
Advanced
AustinZ21AustinZ21
4

speckit-checklist

Generate custom checklists to validate feature requirement quality in spec-kit projects.

Community
Advanced