verification-before-completion-extras

Verify delegated work against output artifacts and dependency freshness checks.

Updated Nov 24, 2025
One-click install
npx skills add https://github.com/ByronWilliamsCPA/.claude --skill verification-before-completion-extras
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion-extras
Source: https://github.com/ByronWilliamsCPA/.claude/tree/main/.claude/skills/verification-before-completion-extras
Command: npx skills add https://github.com/ByronWilliamsCPA/.claude --skill verification-before-completion-extras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common problem of accepting unverified completion, handoff, and derivation claims that lead to defective deliverables, rework, and incorrect downstream outputs. Without falsifiable verification, teams often trust narrative status updates instead of checking actual output artifacts, missing missing work, stale data, or broken guards.

Core Features & Use Cases

  • Artifact-Anchored Handoff Verification: Validate delegated or parallel work against named output artifacts instead of trusting handoff narratives, ensuring no missing or partial work is accepted as complete.
  • Dependency-Graph Freshness Checks: Determine if outputs are current by analyzing read/write dependencies between artifacts instead of relying on unreliable file timestamps.
  • Detector Efficacy Validation: Prove that guards, regression tests, and other checks actually catch intended defects by running them against known broken states, not just clean inputs.
  • Use Case: When a subagent hands off a financial model report claiming it is complete, use this Skill to verify the actual output file exists, contains all required candidate data, and that any attached guard tests fail on known defective model states before accepting the deliverable.

Quick Start

Use the verification-before-completion-extras skill to validate that a delegated team's completed deliverable matches the required output artifact and includes all expected data points before accepting the handoff.

Frequently Asked Questions about verification-before-completion-extras

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

FAQPage Schema
How do I verify artifact handoff completion without relying on status narratives?

Artifact-anchored verification validates delegated work by checking named output artifacts directly, ensuring no missing or partial work is accepted as complete without falsifiable proof points.

What is the best way to check dependency graph freshness for derived statistics?

Dependency-graph freshness checks analyze read/write dependencies between artifacts to determine if outputs are current, replacing unreliable file timestamp comparisons with structural validation.

How do I prove regression test efficacy against known broken states?

Detector efficacy validation runs guards and regression tests against known defective model states to prove they catch intended defects, rather than only testing clean inputs.

Why does my deliverable validation pass but downstream outputs are still defective?

Consumer-contract-derived validation gates tie completion claims to auditable external proof points, preventing defective deliverables caused by trusting narrative status updates over actual artifact verification.

Can I use dependency graph checks for templated report token fills?

Yes, verification of templated report token fills validates that derived outputs match required artifacts and include all expected data points before accepting the deliverable.

When do I need falsifiable artifact anchoring for parallel work acceptance?

Falsifiable artifact anchoring is needed when accepting delegated parallel work, validating statistics from frozen models, or proving guard efficacy to eliminate unplanned rework from unverified claims.