Maintain a verification skill

A feature map rots the moment the app changes. This skill is the upkeep loop for a skill generated by /create-verification-skill (or any project-local verification skill with a feature map). The unit of rigor is the feature, not every sentence: cover every feature file from source and exercise every feature live, without terminalising every bullet.

Outcomes

Pick one, and say which:

• clean: every feature got source and live coverage; nothing worth shipping. No branch, no PR.
• changed: one PR ships proven doc, harness, or map corrections.
• blocked: coverage could not finish or a proven fix could not ship safely. Say exactly what blocked it.

Edit scope

Only edit the verification skill's own directory (its SKILL.md, features/, and any harness scripts it owns), plus the .claude/skills symlink if step 0 finds it broken. Never edit product code during a run: a behavior the map describes that the app no longer does is either doc drift (fix the map) or a product regression (report it, don't paper over it in docs).

Pass

0. Locate the target. Find the verification skill to maintain: the project-local skill whose body has launch/drive sections and a feature map, usually .agents/skills/verify-*/. Also check .claude/skills/verify-*/ and .cursor/skills/verify-*/, and dedupe candidates by resolved real path, since .claude/skills is normally a symlink to the same directory. Several distinct candidates: ask which one. None: stop and point at /create-verification-skill instead of inventing a target. If the canonical copy lives in .agents/skills/ but is not reachable from .claude/skills/, repair it with a relative symlink (ln -s ../.agents/skills .claude/skills, or ln -s ../../.agents/skills/verify-<app> .claude/skills/verify-<app> when .claude/skills is a real directory). If the only copy is a real directory under .claude/skills/ or .cursor/skills/, maintain it in place and tell the user it is not in the canonical .agents/skills/ location; don't move it unasked.