verify-by-failurelisted
Install: claude install-skill sergeykrin9/verify-by-failure
# Verify by failure
A green test proves almost nothing. A watchdog that never fires looks identical to a
watchdog that works. The loop below exists because both of those cost me a production
outage that lasted 46 days.
Use it for any task of three or more steps.
---
## Step 0. Plan with visible progress — before the first action
Three steps or more means a plan first, work second. The person you report to should be
able to see movement without reading your prose.
**If `TodoWrite` is available**, keep the plan there. One item `in_progress` at a time.
**If it isn't** (it is not connected in every session), draw the progress in text.
A compact block at the top of any reply where something moved:
```
▓▓▓▓▓▓▒░░░ step 3 of 5 · 60%
✓ Measured the queue — 132 developers with no dossier
✓ Research: Capstone Asset, LKF Properties
▸ Writing dossiers, verifying against the matcher ← now
Refreshing the open-questions list
Writing the log entry
```
Rules for the block:
- Ten characters exactly: `▓` done, `▒` in flight, `░` ahead.
- Always **both** the step count and the percentage. One answers "how much is left",
the other answers "where am I".
- Phrase items by **outcome** ("dossiers written and matched"), never by action
("search the web").
- Found new work along the way? Add the item and recompute — don't hide it.
- Keep it short. It replaces narrating your progress; it doesn't accompany it.
For long-running work spanning many sessions, show two levels:
```
▓▓▓▓▓