sb-verify-completion

Verifies explicit completion claims against fresh evidence without changing state.

Updated Jul 17, 2026
One-click install
npx skills add https://github.com/Huruikagi/pc-build-planner --skill sb-verify-completion-huruikagi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sb-verify-completion
Source: https://github.com/Huruikagi/pc-build-planner/tree/main/.agents/skills/sb-verify-completion
Command: npx skills add https://github.com/Huruikagi/pc-build-planner --skill sb-verify-completion-huruikagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams and AI agents often accept completion claims based on stale reports, partial evidence, or a subagent's word, leading to false confidence that work is done. This Skill forces every explicit completion or success claim to be checked against freshly reproduced evidence before it is trusted. ## Core Features & Use Cases - Claim-First Verification: Restates the claim in its narrowest form, then demands evidence covering exactly that claim — not a broader or smaller one. - Three-Way Verdict: Returns VERIFIED, NOT_VERIFIED, or MANUAL_VERIFY_REQUIRED, keeping 'could not check' strictly separate from 'checked'. - Consequence-Free Operation: Writes nothing, mutates nothing, and never advances a Spec — completion recording is explicitly delegated to a separate validation workflow. - Use Case: A subagent reports that a bug fix passed all tests. Before accepting that, run this Skill to re-execute the tests yourself and confirm the evidence covers the exact claim being made. ## Quick Start Use the sb-verify-completion skill to verify the claim that the recent fix passes all tests before we mark the task done.

Frequently Asked Questions about sb-verify-completion

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

FAQPage Schema
How do I verify a completion claim before marking a task done?▼

State the claim in its narrowest form, then reproduce the check yourself rather than trusting a report. Return a verdict of VERIFIED, NOT_VERIFIED, or MANUAL_VERIFY_REQUIRED based only on evidence you directly observed.

What is the difference between sb-verify-completion and sb-validate-implementation?▼

sb-verify-completion checks a single claim consequence-free and changes nothing. sb-validate-implementation is the Spec completion gate that records completion evidence through a handshake covering gate freshness, contract review, and milestone convergence.

Can this skill record completion evidence or advance a Spec?▼

No. It is explicitly consequence-free: it writes no artifacts, updates no task progress, and records no completion evidence. A VERIFIED verdict means the claim is supported, not that the Spec may advance.

When should I return MANUAL_VERIFY_REQUIRED instead of VERIFIED?▼

Return MANUAL_VERIFY_REQUIRED when a mandatory check cannot be performed in the current environment, such as evidence from another run you cannot reproduce. It is never a softer NOT_VERIFIED and never a route to VERIFIED.

Why does verification fail when a subagent reports success?▼

A report is a claim, not evidence. The most common false completion is evidence for a part being accepted for the whole, so the check must be rerun directly and the claim scoped precisely before any verdict.