| 1 | --- |
| 2 | name: verify |
| 3 | description: Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification. |
| 4 | invocation: model+user |
| 5 | aliases-for: check-work |
| 6 | --- |
| 7 | |
| 8 | # Verify |
| 9 | |
| 10 | ## When to use |
| 11 | Use when the user wants proof the real surface works, not only unit tests. |
| 12 | |
| 13 | ## Non-goals |
| 14 | - Unit tests alone are not end-to-end verification. |
| 15 | - Do not fake success without observable evidence. |
| 16 | |
| 17 | ## Workflow |
| 18 | 1. Identify the real entrypoint (CLI binary, API, UI). |
| 19 | 2. Exercise it with realistic inputs. |
| 20 | 3. Capture outputs, exit codes, logs, or screenshots. |
| 21 | 4. Report evidence and remaining uncertainty. |
| 22 |