verification-before-completion

# Verification Before Completion

Evidence before claims, always. No completion claims without fresh verification.

## Purpose

Claiming work is done without verification breaks trust and wastes time. This
skill enforces running verification commands and confirming output before any
success claim. "It should work" is not verification.

## The Iron Law

**NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE.**

Every claim must be backed by evidence you just observed. Not evidence from
earlier. Not evidence you expect. Evidence you just saw.

## The Five-Step Gate

Before any completion claim, complete these steps:

### Step 1: Identify

What command proves your claim?

```text
Claim: "Tests pass"
Command: npm test (or project's test command)

Claim: "Build succeeds"
Command: npm run build (or project's build command)

Claim: "Lint is clean"
Command: npm run lint (or project's lint command)

Claim: "Bug is fixed"
Command: The reproduction steps that previously failed
```

### Step 2: Run

Execute the command freshly. Not from cache. Not from memory.

```text
Run the command NOW.
Wait for it to complete.
Do not proceed until finished.
```

### Step 3: Read

Read the COMPLETE output.

```text
- Exit code (0 = success)
- All output lines, not just the last one
- Any warnings (not just errors)
- Summary statistics if provided
```

### Step 4: Verify

Confirm the output supports your claim.

```text
Claim: "Tests pass"
Verify: Exit code 0, "X tests passed", no failures

Claim: "Build succeeds"
Verify: Exit code 0, output files created, no errors

Claim: "Bug is fixed"
Verify: Previous failure no longer occurs
```

### Step 5: Claim

Only NOW make your completion claim.

```text
"Tests pass" - after seeing test output showing success
"Build succeeds" - after seeing build complete without errors
"Implementation complete" - after all verifications pass
```

## Common Failure Modes

### Tests

```text
What to run: Project test command
What to verify:
- Exit code 0
- All t