wz:verification

Enforce completion claims with fresh command evidence or deterministic proof paths.

3|1|Updated Mar 16, 2026

Search Tags:#automation #workflow #verification #evidence #quality-assurance #software-engineering #proof

Ready to run

npx skills add https://github.com/MohamedAbdallah-14/Wazir --skill wz-verification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wz:verification
Source: https://github.com/MohamedAbdallah-14/Wazir/tree/main/skills/verification
Command: npx skills add https://github.com/MohamedAbdallah-14/Wazir --skill wz-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Every completion claim must be backed by fresh command evidence or a deterministic proof path to ensure integrity and traceability.

Core Features & Use Cases

Enforces canonical verification gates before closure of tasks.
Guides collection of reproducible proof artifacts using a standardized workflow.
Integrates automated evidence gathering (proof-collector) to enable verifiable sign-off.
Applicable to software development, project governance, and QA workflows requiring verifiable validation.

Quick Start

Follow the Verification guidelines and collect fresh evidence using the proof-collector before marking a task complete.

Frequently Asked Questions about wz:verification

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

FAQPage Schema

How do I enforce fresh evidence for task completion verification in software engineering?▼

Task completion verification requires fresh command evidence or a deterministic proof path to ensure integrity. This skill enforces canonical verification gates and guides collection of reproducible proof artifacts using a standardized workflow before sign-off.

What is the best way to automate evidence collection for project governance sign-off?▼

Automated evidence collection for project governance sign-off uses a proof-collector mechanism to gather verifiable artifacts. This ensures reproducibility and traceability by enforcing that every completion claim is backed by deterministic proof paths before closure.

How do I set up verification gates for QA workflows requiring reproducible proof artifacts?▼

Verification gates for QA workflows are set up by following standardized guidelines and collecting fresh evidence using a proof-collector. This structured proof-collection workflow ensures reproducibility and verifiable validation before marking a task complete.

When do I need deterministic proof paths for task closure workflows?▼

Deterministic proof paths for task closure workflows are needed when verifiable proofs are required before sign-off. They ensure integrity and traceability in software development, project governance, and quality assurance by backing every completion claim with fresh command evidence.

Can I use this verification workflow for software development and project governance simultaneously?▼

Yes, this verification workflow applies to software development, project governance, and QA workflows. It enforces canonical verification gates and integrates automated evidence gathering to enable verifiable sign-off across these domains requiring verifiable validation.

Why does task verification require fresh command evidence instead of historical logs?▼

Task verification requires fresh command evidence to ensure integrity and traceability. Historical logs lack the deterministic proof path necessary to guarantee reproducibility, whereas fresh evidence validates that every completion claim is currently accurate before sign-off.