maintain-verification-skill

Audits and updates a project's verification skill and feature map through source review and live testing.

2|Updated Sep 14, 2026
One-click install
npx skills add https://github.com/kwanpham2195/agent-stuff --skill maintain-verification-skill-kwanpham2195
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maintain-verification-skill
Source: https://github.com/kwanpham2195/agent-stuff/tree/main/skills/maintain-verification-skill
Command: npx skills add https://github.com/kwanpham2195/agent-stuff --skill maintain-verification-skill-kwanpham2195

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verification skills and their feature maps drift out of sync with the application as the product changes, leaving stale documentation and untested features. This Skill runs a periodic maintenance pass that re-verifies every feature against source code and live behavior, then ships proven corrections. ## Core Features & Use Cases - Parallel source review: Delegates one read-only subagent per feature file to explain how each feature works from source and flag likely documentation drift with citations. - Live verification pass: Drives every feature at least once using browser sessions, TUI sessions, or shell commands, with health checks, evidence preservation, and cleanup invariants. - Scoped corrections: Edits only the verification skill's own directory, triages findings into doc drift, harness gaps, or product bugs, and ships at most one PR of proven fixes. - Use Case: After a month of product changes, run an audit of the project's verify skill to confirm the feature map still matches reality, fix stale entries, and receive a single PR with the corrections. ## Quick Start Ask the agent to audit this project's verification skill and feature map, exercising every feature live and reporting whether the outcome is clean, changed, or blocked.

Frequently Asked Questions about maintain-verification-skill

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

FAQPage Schema
How do I audit a verification skill for documentation drift?▼

Run a maintenance pass that reads each feature file from source with parallel read-only subagents, flags likely drift with citations, then exercises every feature live. Proven corrections ship as one PR limited to the skill's own directory.

How to keep a feature map in sync with a changing application?▼

Use a periodic upkeep loop: fix index hygiene, review every feature from source, sweep recent churn for unmapped user-facing surfaces, and drive each feature live. The unit of rigor is the feature, not every sentence in the docs.

Can this skill modify product code during an audit?▼

No, edits are restricted to the verification skill's own directory, including its SKILL.md, features, and harness scripts. Behavior the app no longer performs is treated as doc drift or reported as a product regression, never patched in product code.

What happens when a feature cannot be reached during live verification?▼

The feature is marked verified-unreachable only with the concrete prerequisite, such as auth, entitlement, OS, or external state, plus the route attempted. If the map omits that prerequisite, the omission itself is recorded as drift.

What are the possible outcomes of a verification skill audit?▼

Every run ends as clean, changed, or blocked. Clean means full coverage with nothing to ship, changed means one PR of proven corrections, and blocked means coverage or a fix could not complete, with the exact blocker stated.