maintain-verification-skill

Audits and updates a project's verification skill and feature map against live application behavior.

6.6k|542|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/cursor/plugins --skill maintain-verification-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maintain-verification-skill
Source: https://github.com/cursor/plugins/tree/main/pstack/skills/maintain-verification-skill
Command: npx skills add https://github.com/cursor/plugins --skill maintain-verification-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature maps and verification skills drift out of sync with the application as code changes, leaving documentation that describes behavior the app no longer has. This Skill runs a periodic maintenance pass that re-verifies every documented feature from source and live execution, then ships only proven corrections.

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.
  • Live verification pass: Drives every feature in a real running session (server, UI, or CLI) with health-check, evidence-preservation, and cleanup invariants held throughout.
  • Scoped corrections: Edits only the verification skill's own directory and ships at most one PR of proven doc, harness, or map fixes, reporting product bugs instead of patching over them.
  • Use Case: After a month of feature development, run the maintenance pass to confirm the verification skill's feature map still matches reality, fix drifted entries, and open a single PR with the corrections.

Quick Start

Ask the agent to run /maintain-verification-skill to audit the project's verification skill and feature map against the current application.

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 the maintain-verification-skill pass, which reads every feature file from source with parallel subagents, exercises each feature live, and ships one PR of proven corrections. It reports clean, changed, or blocked as the outcome.

How to audit documentation drift against actual app behavior?

The skill compares documented feature behavior against source code and live execution, flagging drift with citations. Wrong user-facing descriptions are fixed as doc drift, while genuinely broken app behavior is reported as a product gap, not edited away.

Does the maintenance pass require running the application live?

Yes, a live pass is mandatory even when the source audit looks clean. The coordinator drives every feature at least once in a real session, following the verification skill's own launch model for servers, UIs, or CLIs.

Can this skill modify product code when it finds bugs?

No, edits are strictly scoped to the verification skill's own directory, including its SKILL.md, feature files, and harness scripts. Actual product bugs are recorded and reported to the user rather than patched or hidden in documentation.

What happens when a feature cannot be reached during verification?

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