# Completion Gate (shared)

Authoritative "before you claim it's done" rule, referenced by the verification,
TDD, code-review, and git-workflow skills.

```text
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
```

Before saying work is complete, fixed, passing, implemented, healthy, or ready:

1. Identify the exact command or artifact that proves the claim.
2. Run it fresh in this session and read the output and exit code.
3. Map the result to the affected `REQ-*` / `IMP-TASK-*` / `EV-*` / `HLT-*` /
   `TRK-*` / `CHG-*` IDs.
4. Update durable state only if the evidence supports it; record an `EV-*`.
5. State the result with the command and outcome — not "should pass".

A request marked `implemented` must carry `graduated_to` links. `prd_gate.py`
enforces this at commit/CI time.

## Tool parity (REQ-115)

An agent-facing feature is not COMPLETE until a tool exposes it. If the
feature adds a capability agents should be able to invoke, the same increment
ships the tool (UTCP-first: a catalog capability, with transports generated
from it) and the coverage map names it in `tool_capabilities`; features with
no agent-invocable surface declare `tool_exemption` with a rationale instead
of silently skipping. `feature_skill_audit.py` enforces both directions —
features without declared tools and tool capabilities no feature claims are
findings. The trigger question: "should an agent be able to invoke this?"