maintain-prove-it
Maintain Prove It
A verification skill goes stale the day the app changes: a route moves, a button gets renamed, a new surface ships with nothing in the skill that reaches it. A stale skill is worse than none, because the next agent will trust it. Every prove run leaves a receipt that shows where the skill struggled. This pass reads those receipts and folds what they learned back into the skill.
Rules for the whole pass
- Only edit the skill's own folder (SKILL.md, scripts/). Never change product code here.
- When the app and the skill disagree, work out which one is wrong. The skill describing something the app no longer does is either drift (the app changed on purpose: fix the skill) or a product bug (the app broke: report it, don't rewrite the skill to match the bug). Read the commit that changed it. If you still can't tell, ask.
- Answer keys are not the skill's steps. The user's spec, the snapshots in
.prove-it/snapshots/and the old system a flow is compared with say what right looks like. A drifted step can be fixed, but an answer key that disagrees with the app is reported to the user, never rewritten to match. Only the user changes one. - Every edit you make to the skill gets proved live before you finish. An unproven edit is just more drift.
- Old verdicts are leads, not evidence. Earlier receipts, closed tickets and status docs tell you where to look. Only this pass's live runs count.
- Never loosen a check to make a flaky step pass. Record the failing run, then decide whether the app has a race or the check is ambiguous.
1. Find the skill
Look for prove-* folders under .claude/skills/ and .agents/skills/, at the repo root and in package folders. Prefer ones with the prove-it: marker comment. The marker says which kind it is: permanent skill (the app, one section per surface) or temporary migration skill (one migration, deleted at its end step). If there are several, ask which. If there are none, stop and suggest /create-prove-it.