maintain-verification-skill

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

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

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, causing stale documentation, broken harnesses, and untested features. This Skill runs a periodic maintenance pass that re-verifies every 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 strict health-check, evidence-preservation, and cleanup invariants. - 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 product changes, run the maintenance pass on your project's verify skill to find that two features were renamed, one harness script broke, and the map missed a new settings page — then receive a single PR with the proven corrections. ## Quick Start Ask the AI 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 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 PR; unproven changes are reported, not committed.

How to audit a verify skill for documentation drift?

Launch one read-only subagent per feature file to explain the feature from source and flag likely drift with citations. Spot-check the cited drift, then confirm findings with a live pass before editing the skill's docs or map.

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

No. The edit scope is limited to the verification skill's own directory, including its SKILL.md, features, and harness scripts. Actual product bugs are recorded and reported to the user, never patched or hidden in documentation.

What happens if 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 feature map omits that prerequisite, the omission itself is treated as drift and corrected.

When should I use maintain-verification-skill versus create-verification-skill?

Use create-verification-skill when no project-local verification skill with a feature map exists yet. Use maintain-verification-skill for periodic upkeep of an existing one, since it locates an existing target and stops if none is found.