---

name: task-completion-verify description: Evidence-based completion claims. Use before claiming work is complete, fixed, or passing - requires running verification commands and confirming output before any success claims.

Verification Before Completion

Claiming work is complete without verification is dishonesty, not efficiency.

Core principle: Evidence before claims, always.

---

The Iron Law

CopyNO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

If you haven't run the verification command in this message, you cannot claim it passes.

---

The Gate Function

CopyBEFORE claiming any status:

1. IDENTIFY: What command proves this claim?
2. RUN: Execute the FULL command (fresh, complete)
3. READ: Full output, check exit code, count failures
4. VERIFY: Does output confirm the claim?
   - If NO: State actual status with evidence
   - If YES: State claim WITH evidence
5. ONLY THEN: Make the claim

Skip any step = lying, not verifying

---

Common Verification Requirements

---

Red Flags - STOP

• Using "should", "probably", "seems to"
• Expressing satisfaction before verification
• About to commit/push/PR without verification
• Trusting agent success reports
• Relying on partial verification
• Thinking "just this once"
• ANY wording implying success without running verification

---

Key Patterns

Tests:

CopyDO:   [Run test] [See: 34/34 pass] "All tests pass"
DON'T: "Should pass now" / "Looks correct"

Regression tests (TDD Red-Green):

CopyDO:   Write -> Run (pass) -> Revert fix -> Run (MUST FAIL) -> Restore -> Run (pass)
DON'T: "I've written a regression test" (without red-green)

Build:

CopyDO:   [Run build] [See: exit 0] "Build passes"
DON'T: "Linter passed" (linter != compiler)

Requirements:

CopyDO:   Re-read plan -> Create checklist -> Verify each -> Report
DON'T: "Tests pass, phase complete"

Agent delegation:

CopyDO:   Agent reports -> Check VCS diff -> Verify changes -> Report
DON'T: Trust agent report

---

Rationalization Prevention

---

When to Apply

ALWAYS before:

• ANY success/completion claims
• ANY expression of satisfaction
• Committing, PR creation, task completion
• Moving to next task
• Delegating to agents

---

Integration

Use with:

• code-test - Run tests before claiming they pass
• code-debug - Verify fix before claiming bug resolved
• task-dispatch - Verify each task before marking complete
• git-worktree-use - Verify baseline before and after