What problem does it solve? Work declared done without direct verification has unknown correctness. This Skill prevents agents and developers from relying on proxies like file mtimes, cached screenshots, compile success, or delegate self-reports, enforcing direct observation of the real artifact before claiming completion. ## Core Features & Use Cases - Direct Verification Principle: After any task, check the real thing—run the feature, read the actual value, inspect the git diff—rather than inferring from indirect signals. - Android UI Verification Path: Routes Android UI and device checks through the android-verify skill (Gradle assemble, then android describe / run / layout / screen), with the P18 rule against claiming coverage that was not run. - Delegation Auditing: When verifying delegated work, inspect actual output artifacts (diffs, file contents, runtime behavior) instead of trusting the delegate's summary. - Scripted Proof: Encourages writing a deterministic re-runnable comparison script whose output serves as a reviewable artifact, committed only for large migrations or ports. ## Quick Start Apply the prove-it-works principle to verify the task just completed by running the actual feature and inspecting the real output before declaring it done.
