maintain-verification-skill

Audits and corrects a project's verification skill and feature map through source review and live app drives.

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

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: 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 instance of the app, enforcing health checks, evidence preservation, and cleanup invariants throughout the run. - Scoped corrections: Edits only the verification skill's own directory, fixing doc drift and harness gaps while reporting product regressions instead of masking them, and ships at most one PR of proven fixes. - Use Case: After a month of product changes, run the maintenance pass to confirm every feature in the map still matches reality, fix stale descriptions, and receive a clean, changed, or blocked outcome report. ## Quick Start Ask the agent to run $maintain-verification-skill to audit the project's verification skill and feature map against the current app behavior.

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 reviews each feature file from source with parallel subagents, then drives every feature live in the app. Confirmed drift is corrected in the skill directory and shipped as one PR of proven fixes.

How does the live verification pass work?▼

The coordinator owns all driving, following the verification skill's own launch model: one long-lived instance for servers and UIs, or fresh sessions for short-lived CLIs. Every feature is exercised at least once with health checks before and after drives.

Can the maintenance pass modify product code?▼

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

What happens when a feature cannot be reached during 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 recorded as drift.

What are the possible outcomes of a maintenance run?▼

A run ends as clean when all features pass with nothing to ship, changed when one PR of proven corrections ships, or blocked when coverage could not finish or a fix could not ship safely, with the exact blocker stated.