Evidence-Based Verification

Validate completed software features with concrete test evidence.

Updated Feb 3, 2026

Search Tags:#testing #documentation #verification #evidence #ci-cd #quality-assurance

Ready to run

npx skills add https://github.com/jason-hchsieh/mycelium --skill evidence-based-verification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Evidence-Based Verification
Source: https://github.com/jason-hchsieh/mycelium/tree/main/skills/workflow/verification
Command: npx skills add https://github.com/jason-hchsieh/mycelium --skill evidence-based-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures completed software features are validated with concrete, verifiable evidence instead of unverified claims.

Core Features & Use Cases

Enforces structured verification workflows (unit, integration, and end-to-end)
Produces verifiable outputs (test results, logs, coverage, and artifacts)
Useful for audits, compliance, and reliable releases

Quick Start

Run a full verification loop on a completed feature and capture the evidence of results.

Frequently Asked Questions about Evidence-Based Verification

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

FAQPage Schema

How do I validate completed software features with concrete test evidence instead of unverified claims?▼

You validate features with concrete test evidence by running structured verification workflows across unit, integration, and end-to-end tests. This process captures test results, exit codes, and coverage data to prove correctness and prevent false success claims during the verification phase.

What is evidence-based verification in CI/CD quality assurance?▼

Evidence-based verification in CI/CD quality assurance is the practice of enforcing structured testing workflows that produce verifiable outputs. It ensures completed features are backed by concrete proof like test logs, artifacts, and coverage data rather than relying on unverified success claims.

How do I enforce structured verification workflows for unit, integration, and end-to-end tests?▼

You enforce structured verification workflows by specifying required commands, expected outputs, and documentation standards for unit, integration, and end-to-end tests. This ensures every test run produces verifiable artifacts, exit codes, and coverage data to reliably prove feature correctness.

Does this verification approach work for compliance audits and reliable software releases?▼

Yes, this verification approach works for compliance audits and reliable releases by producing verifiable outputs like test results, logs, and coverage artifacts. These concrete records provide the necessary documentation to prove software correctness and satisfy audit requirements.

What's the best way to prevent false success claims during the software verification phase?▼

The best way to prevent false success claims during the software verification phase is to require concrete evidence such as test run logs, exit codes, and coverage data. Applying structured verification workflows ensures claims are backed by verifiable test results and documentation.

What test outputs and documentation do I need to prove software feature correctness?▼

To prove software feature correctness, you need verifiable outputs including test results, logs, coverage data, and artifacts. Capturing required commands, exit codes, and documentation during unit, integration, and end-to-end tests provides the concrete evidence needed to validate features.