maintain-verification-skill

1# Maintain a verification skill
2 
3A 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.
4 
5## Outcomes
6 
7Pick one, and say which:
8 
9- **clean** — every feature got source and live coverage; nothing worth shipping. No branch, no PR.
10- **changed** — one PR ships proven doc, harness, or map corrections.
11- **blocked** — coverage could not finish or a proven fix could not ship safely. Say exactly what blocked it.
12 
13## Edit scope
14 
15Only edit the verification skill's own directory (its SKILL.md, features/, and any harness 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 (fix the map) or a product regression (report it, don't paper over it in docs).
16 
17## Pass
18 
190. **Locate the target.** Find the verification skill to maintain: the project-local skill whose body has launch/drive sections and a feature map (usually `verify-*/` in the project's skill folder: `.cursor/skills/`, `.claude/skills/`, `.pi/skills/`, or `.agents/skills/`). Several candidates → ask which one; none → stop and point at `/create-verification-skill` instead of inventing a target.
20…