maintain-verification-skill

Audits a project's verification skill and feature map against source code and live app behavior.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A verification skill's feature map drifts out of date the moment the application changes, leaving stale documentation and broken harness scripts that mislead future verification runs. ## Core Features & Use Cases - Parallel source audit: Launches one read-only subagent per feature file to explain how each feature works from source and flag likely documentation drift with citations. - Mandatory live pass: Drives every feature in a real running session (server, UI, or CLI) following the verification skill's own launch model, with health checks, evidence preservation, and residue cleanup invariants. - Scoped corrections: Ships at most one draft PR of proven doc, harness, or map fixes, editing only the verification skill's own directory and never product code. - Use Case: After a month of product changes, run the maintenance pass to re-verify every mapped feature live, fix drifted descriptions, and report genuine product regressions without papering over them. ## Quick Start Ask the AI to audit the project's verification skill and feature map, exercising every feature live and shipping one PR of proven corrections if anything drifted.

Frequently Asked Questions about maintain-verification-skill

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

FAQPage Schema
How do I keep a verification skill's feature map up to date?▼

Run a maintenance pass that reads every feature file from source with parallel subagents, then exercises each feature live in the running app. Proven documentation or harness corrections ship as a single draft PR.

How to audit a verification skill against actual app behavior?▼

The audit combines a source wave explaining each feature from code with a mandatory live pass driving every feature in a real session. Discrepancies are triaged as doc drift, harness gaps, or product regressions.

Can the maintenance pass fix bugs it finds in the product?▼

No, it never edits product code. Broken app behavior is recorded as a product gap and reported to the user, while only the verification skill's own directory (SKILL.md, features, harness scripts) may be edited.

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

The feature is marked verified-unreachable only with the concrete prerequisite (auth, entitlement, OS, external state) and the route attempted. If the map omits that prerequisite, the omission itself is treated as drift.

When should I run verification skill maintenance?▼

Run it periodically after product changes accumulate, since feature maps rot as the app evolves. It is also appropriate whenever the verify skill's launch or drive steps start failing unexpectedly.