provelisted

# /prove — the burden of proof is on you "I added tests and it passes" is not proof — tests written alongside the code inherit its blindspots and the spec's gaps. Proof is an **artifact a skeptic can inspect**: a screenshot, a captured request/response, a real command's output, a before/after. If you can't produce one, say **"unproven"** — confidence never substitutes for evidence. **Standalone and opt-in only.** This skill never runs as part of `/orca` (or any other skill) automatically. Its place in the flow is a recommended optional step after the build, before submission. **Once invoked, go all-in — do NOT ask permission for the work.** Invoking `/prove` IS the authorization: run the app, capture artifacts, spawn the fresh-eyes sub-agent. The only thing worth pausing for is a genuine blocker (app won't build, missing credential) — ask about the blocker, not about whether to proceed. ## What to prove Take the spec items from the plan file the user names (default: the newest plan in `docs/plans/`). For each item prove two things: 1. **It works** — exercised through the *real* path (run app, driven flow), not a unit test. 2. **It improves the product** — the user-visible win is stated and shown, not just "different." ## Artifact modality follows the change type | Change type | Artifact | |---|---| | UI | Playwright screenshot / driven interaction (see `bank/rules/ui-proof-playwright.md` — reuse the project's e2e harness first; never install new tooling into the