Maintain a verification skill

A feature map rots the moment the app changes. This skill is the upkeep loop for a skill generated by the create-verification-skill skill, or for any project-local verification skill with a feature map. The unit of rigor is the feature. Cover every feature file from source, drive every feature live, and report both in one table. Not every bullet needs its own drive.

Outcomes

The pass ends in exactly one outcome. The coverage table decides which one, not your impression of the run.

• blocked. A feature has no live result, a disposition says harness-gap open, or a proven fix could not ship. Say what blocked it and which features it affects. No PR.
• changed. The verification skill's directory has a diff of proven corrections. One PR.
• clean. Every feature has source and live coverage and the skill's directory has no diff. No branch, no PR.

Product gaps never change the outcome. They are the app's problem and go under the table.

Edit scope

Edit only the verification skill's own directory: its SKILL.md, features/, and any helper scripts it owns. Never edit product code during a run. A behavior the map describes that the app no longer does is either doc drift, which you fix in the map, or a product regression, which you report. Do not paper a regression over in the docs.

The pass