maintain-product-verification

Refreshes an existing verification skill and feature map with an evidence-backed maintenance pass.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/AO-HyS/aohys.com --skill maintain-product-verification-ao-hys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maintain-product-verification
Source: https://github.com/AO-HyS/aohys.com/tree/main/.agents/skills/maintain-product-verification
Command: npx skills add https://github.com/AO-HyS/aohys.com --skill maintain-product-verification-ao-hys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Verification skills and feature maps drift out of sync with the product as code changes, leaving stale coverage claims and untrustworthy evidence. This Skill performs an explicit, on-request maintenance pass that re-validates mapped features and updates only the verification artifacts. ## Core Features & Use Cases - Drift Detection: Reads the current Feature Map, inspects source changes, routes, roles, and fixtures, then identifies where verification coverage no longer matches reality. - Role-Separated Live Verification: Sends neutral execution steps to a Computer Use runner while keeping the acceptance rubric private to an independent judge, using deterministic before/after probes. - Scoped Updates: Updates only the verification skill, harness, feature map, or private evidence, and reports clean, changed, or blocked outcomes without touching product code. - Use Case: After a release changes several dashboard routes, ask for a verification maintenance pass to re-run affected flows, refresh the feature map, and store new evidence under the private verification directory. ## Quick Start Ask the agent to run a verification maintenance pass on the repository's existing verify-product skill and refresh the feature map for the changed routes.

Frequently Asked Questions about maintain-product-verification

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

FAQPage Schema
How do I verify a product feature after code changes?▼

Request an explicit maintenance pass: the skill reads the Feature Map, inspects changed routes and fixtures, reuses the repository harness to run a live pass with before/after probes, and updates the verification artifacts. Coverage is only claimed after an observed run with evidence.

What is the difference between the runner and the judge in verification?▼

The Computer Use runner executes neutral steps and never emits PASS/FAIL verdicts or judges side effects. The orchestrator judge holds the private acceptance rubric and decides semantic acceptance by comparing the rubric against execution evidence and probes.

When should I run verification maintenance instead of full verification?▼

Run it when a repository already has a verify-product skill and you need to refresh coverage, verify a feature, or check for drift. It is an explicit maintenance action, not an automatic step in every feature task.

Does verification maintenance modify product code?▼

No. It updates only the verification skill, harness, feature map, or private evidence. Product defects found during the pass are reported separately with route, reproduction steps, evidence, and impact for the product work queue.

Where is verification evidence stored?▼

Evidence artifacts such as screenshots, recordings, and logs are stored only under $HOME/.development-system/private/verification/<run-id>. They must be credential-free, reversible, and referenced by host-provided paths in the maintenance record.

What happens when verification is blocked by missing credentials?▼

The skill reports a blocked outcome identifying whether the environment, credentials, route, or safety boundary prevents a valid proof. It never claims coverage based on file existence or installed commands alone.