wz:reviewer

Automate adversarial review of implemented work against approved specs and plans.

3|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/MohamedAbdallah-14/Wazir --skill wz-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wz:reviewer
Source: https://github.com/MohamedAbdallah-14/Wazir/tree/main/skills/reviewer
Command: npx skills add https://github.com/MohamedAbdallah-14/Wazir --skill wz-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run adversarial review of implementations to ensure alignment with approved specs, plans, and verification evidence, preventing drift and unverified changes.

Core Features & Use Cases

  • Enforces a two-tier review workflow across final, spec-challenge, plan-review, task-review, and related modes.
  • Aggregates findings from internal and cross-model reviews, records severity, and writes results to phase reports.
  • Provides audit-ready checks and guidance to improve compliance and reduce risk across the pipeline.

Quick Start

Run the reviewer in final mode against a completed task to validate compliance.

Frequently Asked Questions about wz:reviewer

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

FAQPage Schema
How do I automate adversarial review of implemented work against approved specs?

Adversarial review of implemented work is automated by running the reviewer against approved specs, plans, and verification evidence to catch drift, ensure compliance, and document findings across pipeline artefacts.

What is the best way to prevent drift during pipeline verification?

Preventing drift during pipeline verification requires enforcing a two-tier review workflow that aggregates findings from internal and cross-model reviews, records severity, and writes audit-ready results to phase reports.

Can I run a spec-challenge review mode for stage reviews?

Spec-challenge review mode is supported alongside final, plan-review, and task-review modes to orchestrate stage reviews, validate compliance, and record findings directly into phase reports.

How does a two-tier review workflow ensure compliance across plan and verification artefacts?

A two-tier review workflow ensures compliance by comparing implemented work against approved specs and plans, aggregating cross-model findings, and documenting severity to provide audit-ready checks across pipeline artefacts.

Do I need approved specs and plans before running a final verification review?

Approved specs, plans, and verification evidence are required before running a final verification review to successfully catch unverified changes and document compliance findings.

Why does implementation drift occur and how can I document it for phase reports?

Implementation drift occurs when work deviates from approved specs, and you document it by running an adversarial review that records severity and writes audit-ready findings to phase reports.