harness-verify-thorough

Audit software verification workflows and generate structured pass/fail evidence.

Updated Apr 18, 2026

Search Tags:#workflow #verification #audit #artifacts #evidence #falsification #pass-fail

Ready to run

npx skills add https://github.com/ZhaoyuWu/Website-Wzy --skill harness-verify-thorough

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: harness-verify-thorough
Source: https://github.com/ZhaoyuWu/Website-Wzy/tree/main/codex-skills/harness-verify-thorough
Command: npx skills add https://github.com/ZhaoyuWu/Website-Wzy --skill harness-verify-thorough

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a rigorous, multi-layer falsification audit to verify software outcomes with evidence, reducing the risk of unverified results.

Core Features & Use Cases

Multi-layer verification: Define assumptions, invariants, and cross-checks across context, logic, and empirical data.
Artifact-driven reporting: Produces structured evidence blocks and traceable findings for audits of stories, tasks, or workflows.
Use Case: Before releasing a story, trigger a thorough audit to confirm correctness and surface edge-case failures with documented rationale.

Quick Start

Provide the target workflow or story to trigger a thorough audit and generate a pass/fail report with supporting artifacts.

Frequently Asked Questions about harness-verify-thorough

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

FAQPage Schema

How do I automate falsification auditing for software verification workflows?▼

To automate falsification auditing, you trigger a comprehensive audit that applies multi-layer verification across context, logic, and empirical data to produce structured pass/fail evidence with documented rationale.

What is multi-layer verification and when do I need it for release audits?▼

Multi-layer verification defines assumptions, invariants, and cross-checks across context, logic, and empirical data. You need it before releasing a story to confirm correctness and surface edge-case failures with traceable artifacts.

How do I generate structured pass/fail evidence for process validation?▼

You generate structured pass/fail evidence by running a thorough audit on your target workflow or story, which produces structured evidence blocks and explicit risk-based findings for requirements, design, and implementation stages.

Can I use artifact-driven reporting for stories, tasks, and automation triggers?▼

Yes, artifact-driven reporting supports audits for stories, tasks, or verifications requested by users and automation triggers, collecting reproducible steps and traceable findings to satisfy multi-layer verification requirements.

What's the best way to verify software outcomes and reduce unverified results?▼

The best way to reduce unverified results is applying a rigorous falsification audit that cross-checks assumptions and invariants, producing clear risk-based findings with explicit pass/fail rationale and supporting artifacts.