evidence-grounded-completionlisted

# Evidence-Grounded Completion ## Overview A completion claim is a state assertion a reader will rely on. This skill runs the six-step verification protocol from the canonical rule [`governance/evidence-grounded-completion.md`](../../governance/evidence-grounded-completion.md) before any completion claim is emitted. The rule is the source of truth for normative content (framework alignment, exception handling, rationale). This skill is the workflow wrapper: when to invoke the protocol and how to execute it step by step. ## When to Use - Before stating "done", "complete", "completed", "finished", "fixed", "shipped", "ready", "resolved", "addressed", "handled", "all set", "good to go", "validated", "verified" (in the conclusory sense), "confirmed", "looks good", or "LGTM". - Before saying "good catch" in response to a user-reported issue (the phrase implies "I understand the scope and have it under control", which is itself a state assertion). - Before wrapping up a unit of work with a summary message that a reviewer or downstream operator will rely on. - After a gate, lint, audit, or test suite reports green and you are about to claim the underlying work is complete (passing gates prove what gates check, not the whole claim). - Before asserting a factual property of an artefact you have not read: that a file, template, schema, configuration, or document contains, lacks, or requires something, in any phase including research, assessment, planning, or review. Read the artef