# Evidence Before Final

> Prevent claiming completion without proof. Use before final responses, handoffs, releases, or review closure.

- Skill: `lubochka/evidence-before-final` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lubochka/evidence-before-final`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lubochka/evidence-before-final/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: lubochka (https://skillmd.com/u/lubochka)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lubochka/evidence-before-final

---


# Evidence Before Final

## Purpose
Prevent claiming completion without proof.

## When to Use
Use before final responses, handoffs, releases, or review closure.

## Inputs
Commands from the target project profile, changed files, review notes, smoke tests, and generated reports.

## Steps
1. Identify claims that require proof.
2. Run only relevant verification.
3. Separate evidence from approval.
4. Report unchecked risks plainly.

## Gates
Every completion claim has evidence or is marked unverified.

## Evidence
File checks, command outputs, review passes, smoke tests, or manual acceptance records.

## Anti-Patterns
Using screenshots, commits, or reports as automatic approval.

## Related
`claim-verification`, `executor-cannot-self-finish`

