Generate an app verify skill

Leading words: interview the repo, drive like a user, feature map, prove one feature, skills/verify-app.

Every serious project needs a way to launch the app, exercise a feature as a user would, and keep evidence. This skill writes that as skills/verify-<app>/ (Agent Skills path — not .cursor/ only).

Copy these steps into the todo list verbatim. Skip with skip: <reason>.

1. Interview the repo (surface, run, drive, observe, isolate). Ask the user only what you cannot observe.
2. Write skills/verify-<app>/SKILL.md with Launch, Doctor, Drive, Evidence, Cleanup, Helpers. Helpers live under helpers/ (not scripts/). A Launch helper is required even when the app is a one-shot CLI (ready signal = usage line + exit).
3. Seed a feature map (features/README.md + 3–5 user-POV feature files).
4. Run launch → doctor → drive one mapped feature → evidence still exists after cleanup.
5. Point at /refreshing-app-verify.

If the checkout does not start, fix that first (or report it). A skill written against a broken base teaches the wrong steps.