verification-before-completion

Validate success criteria and collect artifacts before task completion.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/michael-conrad/.opencode --skill verification-before-completion-michael-conrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/michael-conrad/.opencode --skill verification-before-completion-michael-conrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Completion claims are often made without verifiable backing, leading to undetected defects and audit risk. This Skill enforces evidence-backed verification before any completion claim, ensuring accountability and traceability for issues and tasks.

Core Features & Use Cases

  • Structural completeness checks ensure all required components exist before proceeding to per-SC verification.
  • Clean-room sub-agent orchestration guarantees isolation and prevents data leakage across verification stages.
  • Automated evidence collection and artifact generation produce auditable PASS/FAIL results for each success criterion.
  • Live-source verification gating ensures that runtime behavior matches the spec, not memory or stored files.

Quick Start

Run verification-before-completion to validate all success criteria and collect artifacts before claiming completion.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I enforce evidence-backed completion claims before releasing software?

Evidence-backed completion claims are enforced by validating all success criteria, collecting artifacts, and ensuring live-source verification before closing tasks or issues. This prevents unverified releases by generating auditable PASS or FAIL results for each requirement.

What is live-source verification gating in software workflows?

Live-source verification gating validates actual runtime behavior against the specification rather than relying on memory or stored files. It acts as a safeguard to confirm system behavior before marking a task complete.

How do I generate audit-ready verification reports for success criteria?

Audit-ready verification reports are generated through automated evidence collection and artifact creation during structural completeness checks. This produces specific PASS or FAIL results for each success criterion to ensure traceability.

Does clean-room sub-agent orchestration prevent data leakage during task verification?

Clean-room sub-agent orchestration guarantees isolation across verification stages to prevent data leakage. It dispatches isolated agents to validate success criteria independently without cross-contaminating evidence collection workflows.

When should I use structural completeness checks before per-SC verification?

Structural completeness checks should be used before per-SC verification to ensure all required components exist. Running them first prevents wasted resources validating success criteria when foundational structural elements are missing.