| name | verification-before-completion |
| description | Verification checklist before marking work complete. Use when: finishing a fix, completing a review finding, validating a build, confirming a refactor. |
Verification Before Completion
Ensures fixes and changes are actually validated before declaring success. Prevents "it compiles so it works" thinking.
Core Principle
Never mark work done based on absence of errors. Verify the positive — confirm the expected behavior exists.
Verification Checklist
Before marking any task complete, verify:
1. Build Verification
2. Behavioral Verification
3. Regression Check
4. Integration Verification
Anti-Patterns
| Anti-Pattern | Reality |
|---|
| "It compiles" | Compilation proves syntax, not correctness |
| "Tests pass" | Tests may not cover the changed path |
| "No errors in output" | Silent failures are the worst failures |
| "Works on my machine" | Check both install contexts |
| "The diff looks right" | Run the code, don't just read it |
When to Use
- After fixing a review finding
- After completing a build/install cycle
- After refactoring code
- Before marking a subagent task as done
