proving-donelisted

# Proving Done ## Overview "Done" is a claim that requires evidence: you ran the commands, read the output, and can show the receipts — not a feeling, not "I think tests pass," not "it worked on my machine." This skill is an eight-item checklist to run before claiming work is complete, fixed, passing, or ready to ship. Each item specifies what to check, how to check it, and what bad looks like. ## The Checklist Run all eight items before claiming completion. Each item specifies what to check, how to check it, and what bad looks like. For trivial changes, see the abbreviated process in the Decision Points section. The examples below use Java/Spring commands (`./gradlew`, `checkstyle`, `application.yml`) because they are concrete, but the checklist is stack-agnostic — substitute your stack's equivalents (`npm test`/`eslint`, `pytest`/`ruff`, `go test`/`go vet`, `cargo test`/`clippy`). The eight items apply to backend, frontend, mobile, and infrastructure work alike. Some items overlap with upstream skills by design — item 4 (plan deviations) revisits territory from `exloom:executing-handoff-plans`, and item 5 (edge cases) revisits `exloom:planning-for-handoff`. When the deviation log is already complete and the edge cases were already decided, these items are 30-second confirmations, not redo-work. They exist as a final net to catch what slipped through — work done without a plan, a deviation logged hastily, an edge case the plan never considered. If an item is genuinely