nw-review-output-format

Structure YAML-based platform review outputs with required fields and approval criteria.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines a standardized YAML-based framework for platform design review outputs, ensuring consistent structure and clear acceptance criteria.

Core Features & Use Cases

  • YAML schema for review data: includes review_id, reviewer, artifact_reviewed, review_date, and status fields.
  • Approval criteria and blocking issues support: captures external validity checks, strengths, issues, DORA metrics, and recommendations.
  • Use Case: architecture teams generate a reproducible review artifact for platform changes.

Quick Start

Run a review draft on the latest design documents to produce a platform review YAML immediately.

Frequently Asked Questions about nw-review-output-format

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

FAQPage Schema
How do I standardize platform design review outputs for consistent governance?▼

Standardize platform design review outputs by applying a YAML-based schema that enforces required fields like name and description, ensuring consistent architecture review artifacts and validation criteria across platform components.

What is the best way to structure architecture design review artifacts?▼

Structure architecture design review artifacts using a YAML schema that captures review_id, reviewer, artifact_reviewed, review_date, and status fields to create a reproducible and standardized governance record.

How do I capture approval criteria and blocking issues in a platform review?▼

Capture approval criteria and blocking issues by structuring the platform review YAML to include external validity checks, strengths, identified issues, DORA metrics, and actionable recommendations.

Can I use YAML to enforce validation criteria for architecture and design workflows?▼

Yes, you can use YAML to enforce validation criteria for architecture workflows by defining a strict schema that details required fields and approval gates for platform design reviews.

When do I need a standardized output format for code review and platform design?▼

You need a standardized output format for platform design when architecture teams require reproducible review artifacts, consistent quality gates, and clear acceptance criteria across multiple platform components.

What limitations exist when using a YAML schema for design review outputs?▼

The YAML schema for design review outputs is limited to structuring governance data such as review metadata, DORA metrics, and approval criteria, and does not execute external validation checks or automate the review process itself.