verification

Enforce evidence-based verification and goal-backward checks in software projects.

Updated Mar 25, 2026

Search Tags:#verification #evidence #quality-assurance #software-engineering #artifact-verification #goal-backward

Ready to run

npx skills add https://github.com/tuanldas/superteam --skill verification-tuanldas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/tuanldas/superteam/tree/main/skills/verification
Command: npx skills add https://github.com/tuanldas/superteam --skill verification-tuanldas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Verification prevents false completion claims by enforcing rigorous, evidence-based checks before marking work as done. It combines goal-backward verification, evidence-before-claims discipline, 4-level artifact analysis, and anti-shortcut rules to ensure outcomes are truly achieved.

Core Features & Use Cases

Enforces goal-backward verification: start from the desired outcome and verify that every artifact and step leads to it.
Enforces evidence-before-claims: require fresh, verifiable outputs before declaring success.
Applies a 4-level artifact verification model (Exists, Substantive, Wired, Data-Flow) to every artifact in a project.
Provides anti-shortcut discipline to avoid verification without real evidence.

Quick Start

Run a verification pass against the latest task artifacts to enforce goal-backward verification and evidence-before-claims.

Frequently Asked Questions about verification

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

FAQPage Schema

How do I prevent false task completion claims in software engineering projects?▼

Prevent false completion claims by enforcing evidence-based verification that requires fresh, verifiable outputs before declaring success. This approach stops developers from marking work as done without actual functional artifacts to prove it.

What is goal-backward verification and how does it validate project artifacts?▼

Goal-backward verification starts from the desired outcome and validates that every artifact and step leads to it. It ensures all development workflows, code reviews, and milestone validations connect directly to the project's final objective.

How do I verify software artifacts exist and have proper data flow?▼

Verify software artifacts using a 4-level artifact verification model: Exists, Substantive, Wired, and Data-Flow. This structured discipline ensures real data flows through correctly wired components to produce verifiable outcomes.

What's the best way to enforce evidence-before-claims discipline in code reviews?▼

Enforce evidence-before-claims discipline during code reviews by requiring fresh, verifiable outputs before approving any milestone. This anti-shortcut rule ensures reviewers check real data flows rather than assuming completion claims are accurate.

Can I run artifact verification on development workflows without external dependencies?▼

Yes, you can run artifact verification on development workflows entirely without external dependencies. The skill applies an Iron Law and internal wiring discipline to check milestone validations using only your existing project artifacts.