What problem does it solve? Projects often lack a scripted way to prove that the real app behaves correctly from a user's perspective. This Skill interviews a repository and generates a harness-agnostic verification skill (SKILL.md plus a feature map) that launches the app, drives features programmatically, and captures evidence. ## Core Features & Use Cases - Repo Interview: Detects the app's surface, run command, drive mechanism, observable evidence, and isolation constraints directly from the codebase. - Skill Generation: Writes a canonical docs/verify-<app>/SKILL.md with Launch, Doctor, Drive, Evidence, Cleanup, and Helpers sections, plus thin harness delegates for Cursor, Claude Code, or Codex. - Feature Map Seeding: Creates one file per user-facing feature with a fixed four-heading structure, then proves the generated skill by executing it end to end. - Use Case: An Android project has no scripted UI verification. Run this Skill to generate a verify-<app> skill that assembles via Gradle, drives the app with the android CLI, and captures layout JSON and screen PNGs as proof. ## Quick Start Ask the agent to create a verification skill for this repository so the app can be driven and proven like a real user would.